February 2018 - infinispan-issues

[JBoss JIRA] (ISPN-7470) Distributed executor does not fail over unless future.get() is called

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7470?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7470: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Distributed executor does not fail over unless future.get() is called > --------------------------------------------------------------------- > > Key: ISPN-7470 > URL: https://issues.jboss.org/browse/ISPN-7470 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.6.Final, 9.0.0.CR1 > Reporter: Dan Berindei > Assignee: William Burns > Fix For: 9.3.0.Final > > > After ISPN-6392, {{DistributedExecutorService.submit(...)}} nominally returns a {{CompletableFuture}}. However, it doesn't behave like a regular {{CompletableFuture}}, because it doesn't run the failure policy until the user calls {{future.get()}}. > {{future.isComplete()}} will return {{true}} before running the failure policy, and {{future.whenComplete(callback)}} will also execute the callback before running the failure policy. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7415) Immortal entries use EmbeddedExpirableMetadata instead of EmbeddedMetadata

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7415?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7415: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Immortal entries use EmbeddedExpirableMetadata instead of EmbeddedMetadata > -------------------------------------------------------------------------- > > Key: ISPN-7415 > URL: https://issues.jboss.org/browse/ISPN-7415 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.3.0.Final > > > The default lifespan and maxIdle are -1 to signal no expiration, but calling {{EmbeddedMetadata.Builder.lifespan\(x)}} with any value will make it create an {{EmbeddedExpirableMetadata}} instance. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7407) Investigate flow control performance

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7407?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7407: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Investigate flow control performance > ------------------------------------ > > Key: ISPN-7407 > URL: https://issues.jboss.org/browse/ISPN-7407 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.3.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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.3.0.Final (was: 9.2.0.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 > Fix For: 9.3.0.Final > > > See here https://cwiki.apache.org/confluence/display/solr/The+Standard+Query+Parser -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[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.3.0.Final (was: 9.2.0.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 > Fix For: 9.3.0.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.5.0#75005)

8 years, 1 month

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.3.0.Final (was: 9.2.0.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 > Assignee: Sebastian Łaskawiec > Fix For: 9.3.0.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.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7634) SerializationConfiguration.advancedExternalizers() map should not be mutable

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7634?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7634: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > SerializationConfiguration.advancedExternalizers() map should not be mutable > ---------------------------------------------------------------------------- > > Key: ISPN-7634 > URL: https://issues.jboss.org/browse/ISPN-7634 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Core > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.3.0.Final > > > Currently {{SerializationConfiguration.advancedExternalizers()}} returns a mutable {{HashMap}}. We only read it once on startup, so modifying it won't break anything, but it should be immutable to make it clear that externalizers cannot be added at runtime. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7861) ISPN028502: Unknown alias - when Group By with advanced where clause

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7861?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7861: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > ISPN028502: Unknown alias - when Group By with advanced where clause > -------------------------------------------------------------------- > > Key: ISPN-7861 > URL: https://issues.jboss.org/browse/ISPN-7861 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 9.0.0.Final > Reporter: Gregory Orciuch > Assignee: Adrian Nistor > Fix For: 9.3.0.Final > > > Link to forum: [ISPN028502: Unknown alias - when Group By with advanced where clause|https://developer.jboss.org/thread/275039] > https://developer.jboss.org/thread/275039 > #freenode/infinispan > [17:06] <+anistor> GregoryO_: hi, looks like a bug. could you please file it in Jira? no need to copy the full description, just point to the forum. > [17:06] <+anistor> GregoryO_: thanks! > [17:06] <+anistor> GregoryO_: I'll have a look soon -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7859) Return proper 2XX codes in REST PUT/POST methods

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7859?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7859: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Return proper 2XX codes in REST PUT/POST methods > ------------------------------------------------ > > Key: ISPN-7859 > URL: https://issues.jboss.org/browse/ISPN-7859 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.1.0.Final > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Fix For: 9.3.0.Final > > > The REST interface currently returns only 200 on PUT/POST calls. We should adjust it to 201, 204 and 200. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-7831) Administration console - adjust node memory graph to match PatternFly widget

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7831?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7831: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Administration console - adjust node memory graph to match PatternFly widget > ----------------------------------------------------------------------------- > > Key: ISPN-7831 > URL: https://issues.jboss.org/browse/ISPN-7831 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 9.0.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Minor > Fix For: 9.3.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2018