January 2019 - infinispan-issues - Jboss List Archives

[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.7.Final (was: 9.4.6.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.7.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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7943) Test remote continuous query in compat mode with jboss marshalling

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7943?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7943: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Test remote continuous query in compat mode with jboss marshalling > ------------------------------------------------------------------ > > Key: ISPN-7943 > URL: https://issues.jboss.org/browse/ISPN-7943 > Project: Infinispan > Issue Type: Task > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.7.Final > > > Remote CQ was only tested with Protobuf. We did not initially aim at making this work without protobuf (ie using java serialization/jboss marshalling) but it seems it should work out of the box. We just need to add a test to prove this, and then document it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[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.7.Final (was: 9.4.6.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.7.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, 5 months

1
0
0 / 0

[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.7.Final (was: 9.4.6.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.7.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, 5 months

1
0
0 / 0

[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.7.Final (was: 9.4.6.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.7.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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8196) Activation should occur at the primary node with shared stores

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8196?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8196: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Activation should occur at the primary node with shared stores > -------------------------------------------------------------- > > Key: ISPN-8196 > URL: https://issues.jboss.org/browse/ISPN-8196 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 9.1.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 9.4.7.Final > > > When a cache has passivation enabled and a shared store, any misses on the backup node should result in a call to the primary owner who will then attempt activation from the shared store. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8192) Deprecate redundant methods in CollectionFactory

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8192?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8192: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Deprecate redundant methods in CollectionFactory > ------------------------------------------------ > > Key: ISPN-8192 > URL: https://issues.jboss.org/browse/ISPN-8192 > Project: Infinispan > Issue Type: Task > Affects Versions: 9.1.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 9.4.7.Final > > > Many of the methods in CollectionFactory are redundant and do not add any value. We should deprecate these and replace their use within our code. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8236) Expose score in query results over Hot Rod

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8236?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8236: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Expose score in query results over Hot Rod > ------------------------------------------ > > Key: ISPN-8236 > URL: https://issues.jboss.org/browse/ISPN-8236 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.7.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8238) Add spatial support to Ickle language

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8238?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8238: ---------------------------------- Fix Version/s: 9.4.7.Final (was: 9.4.6.Final) > Add spatial support to Ickle language > ------------------------------------- > > Key: ISPN-8238 > URL: https://issues.jboss.org/browse/ISPN-8238 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.7.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[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.7.Final (was: 9.4.6.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.7.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, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2019