November 2018 - infinispan-issues

[JBoss JIRA] (ISPN-7654) Ickle parser should have a different representation for each literal type instead of using string for everything

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7654?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7654: ---------------------------------- Fix Version/s: 9.4.4.Final (was: 9.4.3.Final) > Ickle parser should have a different representation for each literal type instead of using string for everything > ---------------------------------------------------------------------------------------------------------------- > > Key: ISPN-7654 > URL: https://issues.jboss.org/browse/ISPN-7654 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.4.Final > > > All constant literals regardless of type are represented as string now and are later parsed into integers, booleans, etc, when the query is translated. We should do this at the beginning phase of parsing. See ConstantLiteralTree class. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7643) Coordinator status is unavailable in Infinispan cluster

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7643?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7643: ---------------------------------- Fix Version/s: 9.4.4.Final (was: 9.4.3.Final) > Coordinator status is unavailable in Infinispan cluster > ------------------------------------------------------- > > Key: ISPN-7643 > URL: https://issues.jboss.org/browse/ISPN-7643 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Reporter: Sebastian Łaskawiec > Priority: Major > Fix For: 9.4.4.Final > > > It seems that Coordinator field uses JGroups Address class which can be displayed properly. Since we already have a Coordinator Address field, maybe the best way would be to remove this from JMX. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7606) DistributedExecutorMassIndexer.executeInternal should use an existing pool

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7606?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7606: ---------------------------------- Fix Version/s: 9.4.4.Final (was: 9.4.3.Final) > DistributedExecutorMassIndexer.executeInternal should use an existing pool > -------------------------------------------------------------------------- > > Key: ISPN-7606 > URL: https://issues.jboss.org/browse/ISPN-7606 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 9.4.4.Final > > > {{DistributedExecutorMassIndexer.executeInternal}} creates 2 executors: > 1. {{new DefaultExecutorService(cache)}} implicitly creates a single-threaded executor to run tasks on the local node. > 2. {{compositeFuture.whenCompleteAsync(consumer, Executors.newSingleThreadExecutor())}} explicitly creates a new single-threaded executor to run the consumer on. > Neither of these executors are shut down, and rather than complicating the code to stop them properly it would be better to use an existing executor. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7590) Invocation idempotence

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7590?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7590: ---------------------------------- Fix Version/s: 9.4.4.Final (was: 9.4.3.Final) > Invocation idempotence > ---------------------- > > Key: ISPN-7590 > URL: https://issues.jboss.org/browse/ISPN-7590 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.0.0.CR2 > Reporter: Radim Vansa > Assignee: Radim Vansa > Priority: Major > Labels: consistency > Fix For: 9.4.4.Final > > > This is an umbrella JIRA to change the way how we deal with retries after topology change. > Please link any outstanding issues that refer to incorrect return values of command during topology change. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7660) Ickle should implement constant scoring operator (^=) similar to Solr

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7660?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7660: ---------------------------------- Fix Version/s: 9.4.4.Final (was: 9.4.3.Final) > Ickle should implement constant scoring operator (^=) similar to Solr > --------------------------------------------------------------------- > > Key: ISPN-7660 > URL: https://issues.jboss.org/browse/ISPN-7660 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.4.Final > > > See here https://cwiki.apache.org/confluence/display/solr/The+Standard+Query+Parser -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8482) Projection of enum field returns number instead of constant

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8482?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8482: ---------------------------------- Fix Version/s: 9.4.4.Final (was: 9.4.3.Final) > Projection of enum field returns number instead of constant > ----------------------------------------------------------- > > Key: ISPN-8482 > URL: https://issues.jboss.org/browse/ISPN-8482 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 9.2.0.Alpha2 > Reporter: Gustavo Fernandes > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.4.Final > > > Consider the query below where Gender is mapped in protobuf as an {{enum}}: > {code:sql} > select p.gender, count(p.name) from Person p group by p.gender > {code} > The returned projection is numeric rather than MALE/FEMALE. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8453) Commit should fail if cache is in degraded mode

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8453?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8453: ---------------------------------- Fix Version/s: 9.4.4.Final (was: 9.4.3.Final) > Commit should fail if cache is in degraded mode > ----------------------------------------------- > > Key: ISPN-8453 > URL: https://issues.jboss.org/browse/ISPN-8453 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.1.9.Final, 8.2.8.Final, 9.1.2.Final, 9.2.0.Alpha2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 9.4.4.Final > > > When the originator receives a {{CacheNotFoundResponse}} and the cache is in degraded mode, the transaction is marked as partially completed, but the commit completes successfully. > I believe that is not correct, because the originator could crash after the commit but before the merge, and in that case the transaction will not be applied on all the owners. The transaction manager will ignore any commit exception in {{NON_XA}}/{{useSynchronization}} mode, but at least in {{FULL_XA}}/{{NON_DURABLE_XA}} mode we can signal to the user that the transaction may be lost. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8451) Attributes in AttributeSets should state whether they apply globally or per-node

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8451?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8451: ---------------------------------- Fix Version/s: 9.4.4.Final (was: 9.4.3.Final) > Attributes in AttributeSets should state whether they apply globally or per-node > -------------------------------------------------------------------------------- > > Key: ISPN-8451 > URL: https://issues.jboss.org/browse/ISPN-8451 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 9.4.4.Final > > > Add an additional boolean to AttributeDefinition that defines whether the attribute is global or local. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8441) The module spec used by server config of indexed-entities/indexed-entity and modules/module accepts only deployments

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8441?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8441: ---------------------------------- Fix Version/s: 9.4.4.Final (was: 9.4.3.Final) > The module spec used by server config of indexed-entities/indexed-entity and modules/module accepts only deployments > -------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-8441 > URL: https://issues.jboss.org/browse/ISPN-8441 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 9.1.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.4.Final > > > The module name must start with "deployment." due to the use ServiceModuleLoader.moduleServiceName() method to resolve a service name from a module name. This only knows how to handle deployments from 'deployment' dir, regular modules from the 'modules' dir are not handled. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8356) Embedded distribution names are confusing

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8356?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8356: ---------------------------------- Fix Version/s: 9.4.4.Final (was: 9.4.3.Final) > Embedded distribution names are confusing > ----------------------------------------- > > Key: ISPN-8356 > URL: https://issues.jboss.org/browse/ISPN-8356 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Affects Versions: 9.1.1.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 9.4.4.Final > > > The binary distribution names for embedded libraries are confusing: > I propose the following names > > - infinispan-${version}-all.zip -> infinispan-embedded-${version}-all.zip > - infinispan-${version}-minimal.zip -> infinispan-embedded-${version}-minimal.zip > - infinispan-${version}-remote.zip -> infinispan-remote-${version}.zip > The website labelling needs to be modified accordingly too -- 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