[JBoss JIRA] (ISPN-8241) Refactor RocksDB clearThreshold
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-8241?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8241:
----------------------------------
Fix Version/s: 9.4.4.Final
(was: 9.4.3.Final)
> Refactor RocksDB clearThreshold
> -------------------------------
>
> Key: ISPN-8241
> URL: https://issues.jboss.org/browse/ISPN-8241
> Project: Infinispan
> Issue Type: Sub-task
> Components: Loaders and Stores
> Affects Versions: 9.1.0.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 9.4.4.Final
>
>
> Currently the RocksDB store utilises a "clearThreshold" to try to delete entries individually before deleting and re-initiating the database. We should deprecate this threshold and always delete/reinit the database.
> Currently when deleting the database, we utilise Util.recursiveFileRemove which does not confirm that the file has actually been deleted. Instead, we should provide a nio based implementation instead, similar to the one stated [here|https://stackoverflow.com/questions/779519/delete-directories-recurs...]. This has the advantage that an IOException is thrown by java.nio.file.Files::delete
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[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.4.Final
(was: 9.4.3.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.4.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, 6 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.4.Final
(was: 9.4.3.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.4.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, 6 months