October 2019 - infinispan-issues - Jboss List Archives

[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: 10.0.1.Final (was: 10.0.0.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: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.1.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.13.8#713008)

4 years, 11 months

1
0
0 / 0

[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: 10.0.1.Final (was: 10.0.0.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: 10.0.1.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.13.8#713008)

4 years, 11 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: 10.0.1.Final (was: 10.0.0.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: 10.0.1.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.13.8#713008)

4 years, 11 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: 10.0.1.Final (was: 10.0.0.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: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Labels: SearchNG > Fix For: 10.0.1.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 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: 10.0.1.Final (was: 10.0.0.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: 10.0.1.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.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8115) Remove Index.LOCAL

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8115?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8115: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Remove Index.LOCAL > ------------------ > > Key: ISPN-8115 > URL: https://issues.jboss.org/browse/ISPN-8115 > Project: Infinispan > Issue Type: Sub-task > Components: Embedded Querying > Affects Versions: 9.1.0.Final > Reporter: Radim Vansa > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.0.1.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8116) Stream the results of an Infinispan query

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8116?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8116: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Stream the results of an Infinispan query > ----------------------------------------- > > Key: ISPN-8116 > URL: https://issues.jboss.org/browse/ISPN-8116 > Project: Infinispan > Issue Type: Enhancement > Reporter: Nistor Adrian > Priority: Major > Fix For: 10.0.1.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8163) Remove unsupported 'module' xml attribute from cache config element

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8163?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8163: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Remove unsupported 'module' xml attribute from cache config element > ------------------------------------------------------------------- > > Key: ISPN-8163 > URL: https://issues.jboss.org/browse/ISPN-8163 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.1.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 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: 10.0.1.Final (was: 10.0.0.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: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.1.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[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: 10.0.1.Final (was: 10.0.0.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: 10.0.1.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.13.8#713008)

4 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2019