June 2016 - 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-6812) JavaDoc still has references to NotifyingFuture

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6812?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-6812: ------------------------------------- Assignee: Tristan Tarrant > JavaDoc still has references to NotifyingFuture > ----------------------------------------------- > > Key: ISPN-6812 > URL: https://issues.jboss.org/browse/ISPN-6812 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.0.0.Alpha2 > Reporter: Alan Field > Assignee: Tristan Tarrant > > The following classes still refer to {{NotifyingFuture}} in the JavaDoc, even though the code has been changed to use {{CompletableFuture}} : > {{AsyncCache.java}} (5 matches) > {{DistributedExecutionCompletionService.java}} (5 matches) > {{Cache.java}} (6 matches) > It also looks like the {{FutureAssertion.java}} class is no longer needed? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6812) JavaDoc still has references to NotifyingFuture

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6812?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6812: ---------------------------------- Status: Open (was: New) > JavaDoc still has references to NotifyingFuture > ----------------------------------------------- > > Key: ISPN-6812 > URL: https://issues.jboss.org/browse/ISPN-6812 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.0.0.Alpha2 > Reporter: Alan Field > > The following classes still refer to {{NotifyingFuture}} in the JavaDoc, even though the code has been changed to use {{CompletableFuture}} : > {{AsyncCache.java}} (5 matches) > {{DistributedExecutionCompletionService.java}} (5 matches) > {{Cache.java}} (6 matches) > It also looks like the {{FutureAssertion.java}} class is no longer needed? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6812) JavaDoc still has references to NotifyingFuture

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6812?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6812: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4435 > JavaDoc still has references to NotifyingFuture > ----------------------------------------------- > > Key: ISPN-6812 > URL: https://issues.jboss.org/browse/ISPN-6812 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.0.0.Alpha2 > Reporter: Alan Field > > The following classes still refer to {{NotifyingFuture}} in the JavaDoc, even though the code has been changed to use {{CompletableFuture}} : > {{AsyncCache.java}} (5 matches) > {{DistributedExecutionCompletionService.java}} (5 matches) > {{Cache.java}} (6 matches) > It also looks like the {{FutureAssertion.java}} class is no longer needed? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6816) Remove unnecessary packages from Embedded Uber Jar

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-6816: ----------------------------------------- Summary: Remove unnecessary packages from Embedded Uber Jar Key: ISPN-6816 URL: https://issues.jboss.org/browse/ISPN-6816 Project: Infinispan Issue Type: Bug Reporter: Sebastian Łaskawiec Assignee: Sebastian Łaskawiec Priority: Critical Things to be removed for sure: * jboss modules Things to be checked if can be removed: * log4j (impl for sure, api - needs to be checked if JBoss Logging won't crash) * protostream (probably hotrod client needs it) * protobuf (probably hotrod client needs it) Things that need to stay: * hotrod client (remote cache store scenario) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6814) Move all InfinispanLogger.ROOT_LOGGER messages into this class

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-6814?page=com.atlassian.jira.plugin.... ] Vojtech Juranek updated ISPN-6814: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4364/ > Move all InfinispanLogger.ROOT_LOGGER messages into this class > -------------------------------------------------------------- > > Key: ISPN-6814 > URL: https://issues.jboss.org/browse/ISPN-6814 > Project: Infinispan > Issue Type: Task > Components: Server > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6814) Move all InfinispanLogger.ROOT_LOGGER messages into this class

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-6814?page=com.atlassian.jira.plugin.... ] Vojtech Juranek updated ISPN-6814: ---------------------------------- Status: Open (was: New) > Move all InfinispanLogger.ROOT_LOGGER messages into this class > -------------------------------------------------------------- > > Key: ISPN-6814 > URL: https://issues.jboss.org/browse/ISPN-6814 > Project: Infinispan > Issue Type: Task > Components: Server > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6647) DecoratedCache.putForExternalRead method with Metadata ignores Metadata

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6647?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6647: ---------------------------------- Fix Version/s: 9.0.0.Alpha3 8.2.3.Final > DecoratedCache.putForExternalRead method with Metadata ignores Metadata > ----------------------------------------------------------------------- > > Key: ISPN-6647 > URL: https://issues.jboss.org/browse/ISPN-6647 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 8.2.2.Final > Reporter: Karl von Randow > Assignee: Karl von Randow > Priority: Minor > Fix For: 9.0.0.Alpha3, 8.2.3.Final > > > The implementation of the {{putForExternalRead}} method ignores the {{Metadata}} parameter, instead of passing it on to the {{putForExternalRead}} method in the cache implementation. This is no doubt because the cache implementation previously didn't support {{Metadata}} for {{putForExternalRead}}. > I will prepare a PR and attach it to this ticket shortly. It was a gargantuan effort to patch this up, as you'll see! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5209) Ability change cache settings on the fly

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-5209?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-5209: ------------------------------------------- Currently it is possible. Please look at those references: * http://infinispan.org/docs/8.2.x/infinispan_server_guide/infinispan_serve... * http://blog.infinispan.org/2012/06/infinispan-cli.html Updating cluster-wide configuration requires using Domain Mode and one might use CLI or our new Management Console: * https://www.youtube.com/watch?v=m_j3dz4k4xA > Ability change cache settings on the fly > ---------------------------------------- > > Key: ISPN-5209 > URL: https://issues.jboss.org/browse/ISPN-5209 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration > Reporter: Viraj N > Assignee: Sebastian Łaskawiec > Priority: Minor > Fix For: 8.2.2.Final > > > In current Infinispan there is no way to change the configuration after cache is created. It is better if Infinispan allows to change the configuration even after cache is created. This way settings can be changed without restarting application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 June 2016