April 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6504) Try to use the index even if the query matches all entries

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6504?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6504: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/4241 > Try to use the index even if the query matches all entries > ---------------------------------------------------------- > > Key: ISPN-6504 > URL: https://issues.jboss.org/browse/ISPN-6504 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Remote Querying > Affects Versions: 8.2.1.Final, 9.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha2, 8.2.2.Final, 9.0.0.Final > > > A DSL query with no filter clauses will match all entries. In this case we currently run a non-indexed query even if the cache is indexed. > Performance could be improved a bit by using the index if the query has sorting or projections. This should be treated as a special case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

1 week, 6 days

2
1
0 / 0

[JBoss JIRA] (ISPN-2575) KeyTransformer registration is required on all nodes of the cluster, in case of custom keys

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2575?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2575: -------------------------------- Assignee: Adrian Nistor (was: Sanne Grinovero) > KeyTransformer registration is required on all nodes of the cluster, in case of custom keys > ------------------------------------------------------------------------------------------- > > Key: ISPN-2575 > URL: https://issues.jboss.org/browse/ISPN-2575 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Affects Versions: 5.2.0.Beta5 > Reporter: Anna Manukyan > Assignee: Adrian Nistor > Attachments: ClusteredCacheTest.java > > > The case is the following: > I have a clustered cache on which I want to perform a search. I'm doing the following: > I'm initializing SearchManager on node1, I'm registering a custom key transformer for my key using the created searchmanager, but then when I'm trying to put data into the cache on node1 (which is in REPL_SYNC mode with cache on node2), I'm getting the exception: > java.lang.IllegalArgumentException: Indexing only works with entries keyed on Strings, primitives and classes that have the @Transformable annotation - you passed in a class org.infinispan.query.test.CustomKey3. Alternatively, see org.infinispan.query.SearchManager#registerKeyTransformer > When I'm initializing the SearchManager using node2 cache and register the keyTransformer on it as well, then everything works perfectly, even though I am not using the second created SearchManager. > The test which reproduces the issue is attached to the jira. Please see the test case: testSearchKeyTransformer() -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

3 months, 3 weeks

2
1
0 / 0

[JBoss JIRA] (ISPN-10160) Counter manager configs not applied on server

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-10160: ----------------------------------- Summary: Counter manager configs not applied on server Key: ISPN-10160 URL: https://issues.jboss.org/browse/ISPN-10160 Project: Infinispan Issue Type: Bug Components: Clustered Counter, Server Affects Versions: 9.4.12.Final, 10.0.0.Beta3 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 10.0.0.Beta4, 9.4.13.Final The server model for the counter manager is not correctly set up: * attributes are registered as metrics * the add handler ignores attributes * the configurationmanager is not actually configured * the xml writer attempts to serialize attributes from the wrong model nodes -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10159) Counter client does not use CH to locate a counter

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-10159: ----------------------------------- Summary: Counter client does not use CH to locate a counter Key: ISPN-10159 URL: https://issues.jboss.org/browse/ISPN-10159 Project: Infinispan Issue Type: Bug Reporter: Galder Zamarreño Assignee: Pedro Ruivo So when accessing a counter, a penalty network hop can happen as a result of not using CH data to locate the key. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3749) Revisit JGroups Configuration files

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-3749?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-3749. -------------------------------- Fix Version/s: 7.0.0.Final Resolution: Duplicate Issue Fixed as ISPN-4570 > Revisit JGroups Configuration files > ----------------------------------- > > Key: ISPN-3749 > URL: https://issues.jboss.org/browse/ISPN-3749 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 6.0.0.Final > Reporter: Will Burns > Priority: Major > Fix For: 7.0.0.Final > > > Bela mentioned that currently our *-tcp.xml files have UFC defined in them. He no longer has that in his default configuration. We should revisit our configuration files to make sure they are as closely aligned to JGroups as we can. > {quote} > <bela_> I was looking at infinispan master and noticed that the *-tcp.xml configs still have UFC in them > <bela_> This is not something I have in the default configs in JGroups... > <bela_> perhaps this should be changed... > <bela_> pferraro: dberindei wburns ^^^ > * rachmatowicz has quit (Quit: Ex-Chat) > <wburns> bela_ I can't say I know why it is still there, other than it has been there for a while > <bela_> ok, perhaps someone can take a look ? The closer the Infinispan configs are to the JGroups configs, the better > <pferraro> bela_: WF's tcp stack does not have UFC > <bela_> ok, good. But Infinispan does have it > {quote} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10157) Counter client does not use CH to locate a counter

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10157?page=com.atlassian.jira.plugin... ] Pedro Ruivo updated ISPN-10157: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6874, https://github.com/infinispan/infinispan/pull/6873 > Counter client does not use CH to locate a counter > -------------------------------------------------- > > Key: ISPN-10157 > URL: https://issues.jboss.org/browse/ISPN-10157 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Pedro Ruivo > Priority: Major > Labels: rhdemo-2019 > > So when accessing a counter, a penalty network hop can happen as a result of not using CH data to locate the key. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10157) Counter client does not use CH to locate a counter

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10157?page=com.atlassian.jira.plugin... ] Pedro Ruivo updated ISPN-10157: ------------------------------- Status: Open (was: New) > Counter client does not use CH to locate a counter > -------------------------------------------------- > > Key: ISPN-10157 > URL: https://issues.jboss.org/browse/ISPN-10157 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Pedro Ruivo > Priority: Major > Labels: rhdemo-2019 > > So when accessing a counter, a penalty network hop can happen as a result of not using CH data to locate the key. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10157) Counter client does not use CH to locate a counter

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10157?page=com.atlassian.jira.plugin... ] Pedro Ruivo reassigned ISPN-10157: ---------------------------------- Assignee: Pedro Ruivo > Counter client does not use CH to locate a counter > -------------------------------------------------- > > Key: ISPN-10157 > URL: https://issues.jboss.org/browse/ISPN-10157 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Pedro Ruivo > Priority: Major > Labels: rhdemo-2019 > > So when accessing a counter, a penalty network hop can happen as a result of not using CH data to locate the key. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10158) Fix "make image" target for docker w/o multistage build

by Vittorio Rigamonti (Jira)

[ https://issues.jboss.org/browse/ISPN-10158?page=com.atlassian.jira.plugin... ] Vittorio Rigamonti updated ISPN-10158: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-operator/pull/39 > Fix "make image" target for docker w/o multistage build > ------------------------------------------------------- > > Key: ISPN-10158 > URL: https://issues.jboss.org/browse/ISPN-10158 > Project: Infinispan > Issue Type: Feature Request > Components: Operator > Reporter: Vittorio Rigamonti > Assignee: Vittorio Rigamonti > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10158) Fix "make image" target for docker w/o multistage build

by Vittorio Rigamonti (Jira)

[ https://issues.jboss.org/browse/ISPN-10158?page=com.atlassian.jira.plugin... ] Vittorio Rigamonti updated ISPN-10158: -------------------------------------- Status: Open (was: New) > Fix "make image" target for docker w/o multistage build > ------------------------------------------------------- > > Key: ISPN-10158 > URL: https://issues.jboss.org/browse/ISPN-10158 > Project: Infinispan > Issue Type: Feature Request > Components: Operator > Reporter: Vittorio Rigamonti > Assignee: Vittorio Rigamonti > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 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 April 2019