October 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9316) Rewrite Ickle parser on ANTLR 4

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9316?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9316: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Rewrite Ickle parser on ANTLR 4 > ------------------------------- > > Key: ISPN-9316 > URL: https://issues.jboss.org/browse/ISPN-9316 > Project: Infinispan > Issue Type: Bug > 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)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9319) Cache.lock(key) should throw AvailabilityException in degraded mode

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9319?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9319: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Cache.lock(key) should throw AvailabilityException in degraded mode > ------------------------------------------------------------------- > > Key: ISPN-9319 > URL: https://issues.jboss.org/browse/ISPN-9319 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite - Core > Affects Versions: 9.3.0.CR1 > Reporter: Dan Berindei > Priority: Major > Fix For: 10.0.1.Final > > > We need a test for {{cache.lock(key)}} when one of the owners is not an actual member of the cluster and the cache is in degraded mode. {{PartitionHandlingInterceptor}} doesn't handle {{LockControlCommand}} explicitly, so it might end up throwing {{TimeoutException}} after waiting for a new topology. We should make sure it throws an {{AvailabilityException}} instead. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9079) Cache operations during Conflict Resolution phase should force CR on that key

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9079?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9079: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Cache operations during Conflict Resolution phase should force CR on that key > ----------------------------------------------------------------------------- > > Key: ISPN-9079 > URL: https://issues.jboss.org/browse/ISPN-9079 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.1.Final > > > During a partition merge conflict resolution can take a long time when there are many entries, therefore if a user initiates an operation on a key during this phase, it should force CR to occur on the key before executing the operation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9156) Protobuf metadata cache should not have invocation batching enabled

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9156?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9156: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Protobuf metadata cache should not have invocation batching enabled > ------------------------------------------------------------------- > > Key: ISPN-9156 > URL: https://issues.jboss.org/browse/ISPN-9156 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Querying > Reporter: Galder Zamarreño > Assignee: Nistor Adrian > Priority: Major > Labels: redhat-summit-18 > Fix For: 10.0.1.Final > > > As a result of having invocation batching enabled, any update failures would not make the cache operations fail. > Although surprising, that's an expected behaviour of invocation batching. It should be better documented (see [discussion email|https://markmail.org/message/gbvtv6a3w4gtsvj6]). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9161) Description of StateTransferManager attributes does not match the behaviour or show wrong content

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9161?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9161: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Description of StateTransferManager attributes does not match the behaviour or show wrong content > ------------------------------------------------------------------------------------------------- > > Key: ISPN-9161 > URL: https://issues.jboss.org/browse/ISPN-9161 > Project: Infinispan > Issue Type: Bug > Components: Core, Documentation-Core > Reporter: Wolf-Dieter Fink > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.1.Final > > Attachments: Screenshot from 2018-05-16 10-01-28.png > > > Current description is: > If true, the node has successfully joined the grid and is considered to hold state. If false, the join process is still in progress.. > But the behaviour is: > It doesn't wait for the initial state transfer, it just waits for the coordinator to send it a topology before joinComplete is set to TRUE -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9173) Availability mode should be updated atomically with the actual members

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9173?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9173: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Availability mode should be updated atomically with the actual members > ---------------------------------------------------------------------- > > Key: ISPN-9173 > URL: https://issues.jboss.org/browse/ISPN-9173 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.3.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.0.1.Final > > > This is a follow-up on ISPN-7682, which asks for the topology itself to be updated atomically. > {{LocalTopologyManagerImpl}} has additional logic to update the availability mode first when the cache becomes degraded and to update it last when the cache becomes available, which means any delay between the updates cannot cause data inconsistencies. > But that logic doesn't really belong in {{LocalTopologyManagerImpl}}, and it's easy to forget it's there (and in fact we had a bug there related to the new rebalance phases). > In addition, tests that want to check the cache behaviour in degraded mode and wait only for the availability mode change will fail if there's a big delay between the availability mode change. I actually hit this while testing my ISPN-8731/ISPN-7682 changes, and I had added a random delay in {{StateConsumerImpl}} before {{distributionManager.setCacheTopology()}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9132) Migrate from the security vault to credential store

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9132?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9132: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Migrate from the security vault to credential store > --------------------------------------------------- > > Key: ISPN-9132 > URL: https://issues.jboss.org/browse/ISPN-9132 > Project: Infinispan > Issue Type: Enhancement > Components: Test Suite - Server > Affects Versions: 9.3.0.Alpha1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.1.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9177) Add RBAC to admin console pages

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9177?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9177: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Add RBAC to admin console pages > ------------------------------- > > Key: ISPN-9177 > URL: https://issues.jboss.org/browse/ISPN-9177 > Project: Infinispan > Issue Type: Feature Request > Components: Console > Affects Versions: 9.2.3.Final, 9.3.0.Beta1 > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Major > Fix For: 10.0.1.Final > > > Up until now, we have assumed that admin user is able to invoke all operations, access and mutate all data from the admin console. With the advent of data manipulation capabilities in the console (ISPN-8759) and taking into account all existing management operations (some are destructive and irreversible), we should introduce RBAC to admin console page. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9072) Document Protobuf annotated collection null set callbacks

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9072?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9072: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Document Protobuf annotated collection null set callbacks > --------------------------------------------------------- > > Key: ISPN-9072 > URL: https://issues.jboss.org/browse/ISPN-9072 > Project: Infinispan > Issue Type: Task > Components: Documentation-Query > Affects Versions: 9.2.1.Final > Reporter: Galder Zamarreño > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.1.Final > > > When using collection fields in Protobuf annotated classes, empty collections are marshalled into the same value as {{null}}, because Protobuf only has repeated fields and no fields is represented as {{null}}. > This means that if you have an entity with an empty collection, when it's deserialized the collection will be null. This can be confusing for users and should be documented. > [~anistor] had some ideas on how to improve this: > {code} > <anistor> I'm thinking of a way to make this easier for users that > would prefer an empty collection being set instead of a > null. would be possible by adding a new attribute for this in > @ProtoField anotation > > that'd be more predictable > <anistor> would still not give you at deserializtion what was written > during serialization. we do not have a null marker > <anistor> it would just give you an empty collection if you prefer > <anistor> instead of null > > that option should be enabled by default > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9726) Document max clause property on boolean query

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9726?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9726: ---------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Document max clause property on boolean query > --------------------------------------------- > > Key: ISPN-9726 > URL: https://issues.jboss.org/browse/ISPN-9726 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, Remote Querying > Affects Versions: 10.0.0.Alpha1 > Reporter: Katia Aresti > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.1.Final > > > Document the ability to override org.apache.lucene.search.BooleanQuery.maxClauseCount using infinispan.query.lucene.max-boolean-clauses JVM system property. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2019