November 2018 - infinispan-issues

[JBoss JIRA] (ISPN-6224) Simplify configuration of Query with Indexing Affinity

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-6224?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6224: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Simplify configuration of Query with Indexing Affinity > ------------------------------------------------------ > > Key: ISPN-6224 > URL: https://issues.jboss.org/browse/ISPN-6224 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Sanne Grinovero > Priority: Major > Fix For: 9.4.3.Final > > > We should try to enable the "Index Affinity" capabilities in an easier way from a configuration point of view. > For example I wonder if the capabilities provided by the {{AffinityPartitioner}} could not be enabled by default, for example automatically decorating any user defined {{HashFunctionPartitioner}} so that people can't neither forget to enable it, nor override it. > Second, should it be enabled by default when the cache configuration suggests it, for example in most clustered caches? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6219) An interruption during a MassIndexer run should exit early

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-6219?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6219: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > An interruption during a MassIndexer run should exit early > ---------------------------------------------------------- > > Key: ISPN-6219 > URL: https://issues.jboss.org/browse/ISPN-6219 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Reporter: Sanne Grinovero > Priority: Major > Fix For: 9.4.3.Final > > > Methods like {{IndexUpdater.updateIndex()}} correctly check for interruption state to skip some work but they don't trigger an early exit from the indexing loop so we'd still be consuming all of the data stream. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6220) Speedup index rebuilds but using ADD rather than UPDATE statements when safe

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-6220?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6220: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Speedup index rebuilds but using ADD rather than UPDATE statements when safe > ---------------------------------------------------------------------------- > > Key: ISPN-6220 > URL: https://issues.jboss.org/browse/ISPN-6220 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Sanne Grinovero > Priority: Major > Fix For: 9.4.3.Final > > > The {{DistributedExecutorMassIndexer}} relies on update commands to index the new entries, but when we just run a full purge of the index it should be safe to use Add commands instead if we know that there aren't concurrent updates. > The lack of concurrent updates might be tricky but I think we can find such a condition when using Affinity as the index is being fully controlled by the current indexing engine, similarly to the checks to see if it's safe to use an NRT workspace. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6212) InfinispanBackendQueueProcessor is assuming all IndexManager implementations are DirectoryBasedIndexManager

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-6212?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6212: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > InfinispanBackendQueueProcessor is assuming all IndexManager implementations are DirectoryBasedIndexManager > ----------------------------------------------------------------------------------------------------------- > > Key: ISPN-6212 > URL: https://issues.jboss.org/browse/ISPN-6212 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.3.Final > > > See also the FIXME note in {{InfinispanBackendQueueProcessor}}: this needs to be cleaned up. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6172) Drop getBulk and getBulkKeys from Hot Rod protocol

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-6172?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6172: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Drop getBulk and getBulkKeys from Hot Rod protocol > -------------------------------------------------- > > Key: ISPN-6172 > URL: https://issues.jboss.org/browse/ISPN-6172 > Project: Infinispan > Issue Type: Task > Reporter: Tristan Tarrant > Assignee: Galder Zamarreño > Priority: Major > Fix For: 9.4.3.Final > > > Drop getBulk and getBulkKeys from Hot Rod protocol. The same could be achieved with the iterator operation, plus values()/entries, not currently implemented by RemoteCache, could be implemented in terms of iterator as well. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6170) Remove RequestBalancingStrategy from the HotRod client

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-6170?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6170: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Remove RequestBalancingStrategy from the HotRod client > ------------------------------------------------------ > > Key: ISPN-6170 > URL: https://issues.jboss.org/browse/ISPN-6170 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols > Reporter: Tristan Tarrant > Assignee: Galder Zamarreño > Priority: Major > Fix For: 9.4.3.Final > > > Remove RequestBalancingStrategy, deprecated since 7.0, replaced by FailoverRequestBalancingStrategy -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6169) Drop server support for HotRod 1.x

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-6169?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6169: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Drop server support for HotRod 1.x > ---------------------------------- > > Key: ISPN-6169 > URL: https://issues.jboss.org/browse/ISPN-6169 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols, Server > Reporter: Tristan Tarrant > Assignee: Galder Zamarreño > Priority: Major > Fix For: 9.4.3.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6167) Remove deprecated ConsistentHash.init() method from the HotRod client

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-6167?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6167: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Remove deprecated ConsistentHash.init() method from the HotRod client > --------------------------------------------------------------------- > > Key: ISPN-6167 > URL: https://issues.jboss.org/browse/ISPN-6167 > Project: Infinispan > Issue Type: Task > Components: Remote Protocols > Reporter: Tristan Tarrant > Assignee: Galder Zamarreño > Priority: Major > Fix For: 9.4.3.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6479) CacheRpcCommandExternalizer should cache the cache name bytes

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-6479?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6479: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > CacheRpcCommandExternalizer should cache the cache name bytes > ------------------------------------------------------------- > > Key: ISPN-6479 > URL: https://issues.jboss.org/browse/ISPN-6479 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 9.4.3.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6476) Integration test modules shouldn't change the failsafe plugin's lifecycle

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-6476?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6476: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Integration test modules shouldn't change the failsafe plugin's lifecycle > ------------------------------------------------------------------------- > > Key: ISPN-6476 > URL: https://issues.jboss.org/browse/ISPN-6476 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 8.2.1.Final > Reporter: Dan Berindei > Priority: Major > Fix For: 9.4.3.Final > > > Many of our integration tests modules run the {{integration-test}} and {{verify}} goals of {{maven-failsafe-plugin}} together, sometimes specifying a lifecycle phase, sometimes not. This shouldn't be necessary, because failsafe runs both goals, it just binds them to different phases. > On the contrary, running both goals in the same phase can fail the build too early, skipping any executions bound to the {{post-integration-test}} phase. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 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 November 2018