[JBoss JIRA] (ISPN-8003) ProtobufMetadataManagerInterceptor fail the InterceptorDefinesAllReadWritesCheck
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-8003?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8003:
----------------------------------
Fix Version/s: 9.4.8.Final
(was: 9.4.7.Final)
> ProtobufMetadataManagerInterceptor fail the InterceptorDefinesAllReadWritesCheck
> --------------------------------------------------------------------------------
>
> Key: ISPN-8003
> URL: https://issues.jboss.org/browse/ISPN-8003
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 8.2.0.Final, 9.0.0.Final
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Priority: Major
> Fix For: 9.4.8.Final
>
>
> {code}
> ProtobufMetadataManagerInterceptor.java:43, InterceptorDefinesAllReadWritesCheck, Priority: Normal
> Interceptor defines methods [visitPutKeyValueCommand, visitRemoveCommand, visitPutMapCommand, visitReplaceCommand] but does not define [visitReadWriteKeyCommand, visitReadWriteManyCommand, visitReadWriteKeyValueCommand, visitReadWriteManyEntriesCommand] [not required for tests]
> {code}
> {code}
> QueryInterceptor.java:69, InterceptorDefinesAllReadWritesCheck, Priority: Normal
> Interceptor defines methods [visitPutKeyValueCommand, visitRemoveCommand, visitPutMapCommand, visitReplaceCommand] but does not define [visitReadWriteKeyCommand, visitReadWriteManyCommand, visitReadWriteKeyValueCommand, visitReadWriteManyEntriesCommand] [not required for tests]
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 11 months
[JBoss JIRA] (ISPN-7982) Ickle purely negative fulltext subqueries cause empty results
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-7982?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-7982:
----------------------------------
Fix Version/s: 9.4.8.Final
(was: 9.4.7.Final)
> Ickle purely negative fulltext subqueries cause empty results
> -------------------------------------------------------------
>
> Key: ISPN-7982
> URL: https://issues.jboss.org/browse/ISPN-7982
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 9.0.0.Final
> Reporter: Gustavo Fernandes
> Assignee: Adrian Nistor
> Priority: Major
> Fix For: 9.4.8.Final
>
>
> When using parethesis in an Ickle full text predicate, it can generate subqueries that are pure negative, e.g.
> {{from IspnEvent where (tags : ('tagA' and (not 'a0')))}}
> In Lucene, the query
> {{+tags:taga +(-tags:a0)}}
> is different from
> {{+tags:taga -tags:a0}}
> The latter works as expected, but the former brings empty results since Lucene does no support purely negative subqueries. In order for the former query to work, it needs to add all documents as another term to the subquery, for e.g. {{+tags:taga +(\*:\* -tags:a0)}}.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 11 months
[JBoss JIRA] (ISPN-7956) Investigate removing PartitionHandlingInterceptor
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-7956?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-7956:
----------------------------------
Fix Version/s: 9.4.8.Final
(was: 9.4.7.Final)
> Investigate removing PartitionHandlingInterceptor
> -------------------------------------------------
>
> Key: ISPN-7956
> URL: https://issues.jboss.org/browse/ISPN-7956
> Project: Infinispan
> Issue Type: Task
> Components: Core
> Affects Versions: 9.1.0.Beta1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 9.4.8.Final
>
>
> When all the owners of a key leave the cluster, the distribution interceptor doesn't know how to handle that key. Instead, it has to signal that to the {{PartitionHandlingInterceptor}} somehow, and PHI decides whether to return a {{null}} value or throw an {{AvailabilityException}}.
> Single-key read commands and write commands are handled by throwing an {{AllOwnersLostException}} (initially an {{RpcException}}) from the distribution interceptor and catching it in {{PartitionHandlingInterceptor}}. If partitioning handling is disabled, the {{AllOwnersLostException}} is instead caught by {{StateTransferInterceptor}}, which returns the {{null}} value (for read commands) or waits for a new topology and retries (for write commands).
> For multi-key read commands the distribution interceptor can't throw an exception, because that would lose the values that were retrieved successfully. For {{GetAllCommand}} we could get away with storing the values in the context, but that wouldn't work for functional commands because they transform the values on the remote node. ISPN-7884 removing the values with missing owners from the result collection, but that means values that are simply missing have to be treated differently, and {{StateTransferInterceptor}} has to iterate through the list of results again in order to remove them.
> It should be simpler to move all the availability checks to the distribution interceptor, and remove the {{PartitionHandlingInterceptor}}. DI already calls some {{PartitionHandlingManager}} methods directly, in order to keep track of partially committed transactions.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 11 months
[JBoss JIRA] (ISPN-7935) Document Server Tasks
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-7935?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-7935:
----------------------------------
Fix Version/s: 9.4.8.Final
(was: 9.4.7.Final)
> Document Server Tasks
> ---------------------
>
> Key: ISPN-7935
> URL: https://issues.jboss.org/browse/ISPN-7935
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server, Tasks
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Priority: Major
> Fix For: 9.4.8.Final
>
>
> There's literally no documentation on using ServerTask. They're very powerful and we should promote them more since they can act as a stop gap solution for any missing features in HR client.
> I'll add documentation for ServerTasks once Infinispan can execute ServerTasks fine, even if they're POJOs.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 11 months
[JBoss JIRA] (ISPN-7912) Prevent RocksDBStore writes blocking on full expiry queue
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-7912?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-7912:
----------------------------------
Fix Version/s: 9.4.8.Final
(was: 9.4.7.Final)
> Prevent RocksDBStore writes blocking on full expiry queue
> ---------------------------------------------------------
>
> Key: ISPN-7912
> URL: https://issues.jboss.org/browse/ISPN-7912
> Project: Infinispan
> Issue Type: Sub-task
> Components: Loaders and Stores
> Affects Versions: 9.1.0.Alpha1
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 9.4.8.Final
>
>
> Currently you can only insert 10000 elements into the rocks db store until you will block a thread until the expiration reaper is ran. Instead we should offer elements to the queue and upon failure utilise the persistence executors to run purge.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 11 months
[JBoss JIRA] (ISPN-8487) Global MBean registration happens too soon
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-8487?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8487:
----------------------------------
Fix Version/s: 9.4.8.Final
(was: 9.4.7.Final)
> Global MBean registration happens too soon
> ------------------------------------------
>
> Key: ISPN-8487
> URL: https://issues.jboss.org/browse/ISPN-8487
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.2.0.Alpha2
> Reporter: Dan Berindei
> Priority: Major
> Fix For: 9.4.8.Final
>
>
> Currently {{DefaultCacheManager}} explicitly starts {{CacheManagerJmxRegistration}} before calling {{ModuleLifecycle#cacheManagerStarting}}, which means MBeans in other modules are not registered in JMX.
> We should start {{CacheManagerJmxRegistration}} only during global component registry start, after the modules have registered their components. If we want to make the cache manager available in JMX before {{DefaultCacheManager.start()}}, we should only register that particular MBean. Conversely, on shutdown, components other than the cache manager should be removed from JMX on {{DefaultCacheManager.stop()}} (as per ISPN-118).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 11 months