New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ISPN-3902 Upgrade to Apache Lucene 4.6.1 #2338
Conversation
[ERROR] Failed to execute goal on project infinispan-lucene-v4: Could not resolve dependencies for project org.infinispan:infinispan-lucene-v4:jar:7.0.0-SNAPSHOT: The following artifacts could not be resolved: org.apache.lucene:lucene-core:jar:4.6.1, org.apache.lucene:lucene-analyzers-common:jar:4.6.1: Failure to find org.apache.lucene:lucene-core:jar:4.6.1 in http://maven.repository.redhat.com/earlyaccess/all/ was cached in the local repository, resolution will not be reattempted until the update interval of redhat-earlyaccess-repository-group has elapsed or updates are forced -> [Help 1] |
I guess the new artifacts are not published yet. We'll wait... :) |
…or inter-server communication
* changed interface NotifyingNotifiableFuture, implemented in NotifyingFutureImpl * using futures from infinispan-commons (both RemoteCacheImpl and CacheImpl via LegacyNotifyingFutureAdaptor) * reflected API changes to RpcManagerImpl, DistributedExecutorService (split DistributeTaskPart -> Local/Remote) and MapReduceTask
hum, right sorry! I have the staging repositories enabled locally, I shouldn't keep them always enabled. The release is being delayed as a problem was found, I'll send this again when it will be available. |
AssertionError * Fixed issue IBM LRU implementation ** Changed LRU to support Equivalence * Changed EquivalenceHashMap to use buckets instead ** Previous implementation had issue with large entries when re-sort
* Infinispan's Version class reports the wrong version * JmxManagementTest asserts wrong "Version" jmx attribute value for CacheManager mbean * AbstractSingleNodeMemcachedTest asserts the wrong version
…o purge entities in any case
Results in NullPointerException in EquivalentHashMap when receiving an invalidate command during startup. * Initialize the key Equivalence in AbstractInvocationContextFactory in the init() method (instead of start()). * StateTransferLock.waitForTransactionData() should never return before the initial topology was installed. * RpcManagerImpl must set the topology id for non-tx TopologyAffectedCommands that are wrapped in SingleRpcCommands. * Invalidation commands should have their topology id set in StateTransferInterceptor.
…leFile fails randomly
Seems finally available in public repositories! It took 4 release candidates to get it out. |
rebased it |
Integrated in master. Thanks! |
great, thanks @anistor .. this looks like a small thing but paves the road to major cleanups. |
https://issues.jboss.org/browse/ISPN-3902