March 2017 - 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, 5 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, 2 weeks

2
1
0 / 0

[JBoss JIRA] (ISPN-7692) Change eviction chapter to Data Container and reword appropriately

by William Burns (JIRA)

William Burns created ISPN-7692: ----------------------------------- Summary: Change eviction chapter to Data Container and reword appropriately Key: ISPN-7692 URL: https://issues.jboss.org/browse/ISPN-7692 Project: Infinispan Issue Type: Task Components: Documentation-Core Affects Versions: 9.0.0.Final Reporter: William Burns The current eviction chapter contains more broad information regarding how the data container is configured. We should make the chapter about data container and have eviction a subtype under that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7672) NonTotalOrderTxPerCacheInboundInvocationHandler throws warning when adding cache entry using Spring Session

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-7672?page=com.atlassian.jira.plugin.... ] Pedro Ruivo commented on ISPN-7672: ----------------------------------- I've managed to get my branch working and I've created a review PR: https://github.com/infinispan/infinispan/pull/5045 > NonTotalOrderTxPerCacheInboundInvocationHandler throws warning when adding cache entry using Spring Session > ----------------------------------------------------------------------------------------------------------- > > Key: ISPN-7672 > URL: https://issues.jboss.org/browse/ISPN-7672 > Project: Infinispan > Issue Type: Bug > Components: Cloud Integrations, Spring Integration > Affects Versions: 9.0.0.CR4 > Reporter: Sebastian Łaskawiec > Assignee: Galder Zamarreño > Priority: Blocker > Fix For: 9.1.0.Final > > > When I'm trying to add an entry using Spring Session integration with a [transactional cache|https://github.com/slaskawi/presentations/blob/master/2017_spring_s...], the server throws a warning: > {code} > [transactions-repository-1-2cbrv] 06:53:40,773 WARN [org.infinispan.remoting.inboundhandler.NonTotalOrderTxPerCacheInboundInvocationHandler] (remote-thread--p2-t18) ISPN000071: Caught exception when handling command DistributedExecuteCommand [cache=Cache 'sessions'@transactions-repository-1-2cbrv, keys=[], callable=ClusterEventCallable{identifier=b345211e-fbd7-4305-b3a6-6979301e0360, events=[ClusterEvent {type=CACHE_ENTRY_CREATED, cache=Cache 'sessions'@transactions-repository-1-2cbrv, key=[B@8c75820, value=[B@76856353, oldValue=null, transaction=RecoveryAwareGlobalTransaction{xid=< 131077, 29, 36, 0000000000-1-1-84170374-96-629488-44-62370001349, 0000000000-1-1-84170374-96-629488-44-62370001400000000 >, internalId=562954248388609} GlobalTx:transactions-repository-1-cwk6f:1, retryCommand=false, origin=transactions-repository-1-cwk6f}]}]: org.infinispan.commons.CacheListenerException: ISPN000280: Caught exception [java.lang.ClassCastException] while invoking method [public void org.infinispan.server.hotrod.ClientListenerRegistry$BaseClientEventSender.onCacheEvent(org.infinispan.notifications.cachelistener.event.CacheEntryEvent)] on listener instance: org.infinispan.server.hotrod.ClientListenerRegistry$StatelessClientEventSender@7b97a57 > [transactions-repository-1-2cbrv] at org.infinispan.notifications.impl.AbstractListenerImpl$ListenerInvocationImpl$1.run(AbstractListenerImpl.java:401) > [transactions-repository-1-2cbrv] at org.infinispan.util.concurrent.WithinThreadExecutor.execute(WithinThreadExecutor.java:20) > [transactions-repository-1-2cbrv] at org.infinispan.notifications.impl.AbstractListenerImpl$ListenerInvocationImpl.invoke(AbstractListenerImpl.java:419) > [transactions-repository-1-2cbrv] at org.infinispan.notifications.cachelistener.CacheNotifierImpl$BaseCacheEntryListenerInvocation.doRealInvocation(CacheNotifierImpl.java:1512) > [transactions-repository-1-2cbrv] at org.infinispan.notifications.cachelistener.CacheNotifierImpl$BaseCacheEntryListenerInvocation.doRealInvocation(CacheNotifierImpl.java:1508) > [transactions-repository-1-2cbrv] at org.infinispan.notifications.cachelistener.CacheNotifierImpl$BaseCacheEntryListenerInvocation.invokeNoChecks(CacheNotifierImpl.java:1503) > [transactions-repository-1-2cbrv] at org.infinispan.notifications.cachelistener.CacheNotifierImpl.notifyClusterListeners(CacheNotifierImpl.java:711) > [transactions-repository-1-2cbrv] at org.infinispan.notifications.cachelistener.cluster.ClusterEventCallable.call(ClusterEventCallable.java:49) > [transactions-repository-1-2cbrv] at org.infinispan.notifications.cachelistener.cluster.ClusterEventCallable.call(ClusterEventCallable.java:25) > [transactions-repository-1-2cbrv] at org.infinispan.commands.read.DistributedExecuteCommand.invokeAsync(DistributedExecuteCommand.java:99) > [transactions-repository-1-2cbrv] at org.infinispan.remoting.inboundhandler.BasePerCacheInboundInvocationHandler.invokeCommand(BasePerCacheInboundInvocationHandler.java:90) > [transactions-repository-1-2cbrv] at org.infinispan.remoting.inboundhandler.BaseBlockingRunnable.invoke(BaseBlockingRunnable.java:90) > [transactions-repository-1-2cbrv] at org.infinispan.remoting.inboundhandler.BaseBlockingRunnable.runAsync(BaseBlockingRunnable.java:68) > [transactions-repository-1-2cbrv] at org.infinispan.remoting.inboundhandler.BaseBlockingRunnable.run(BaseBlockingRunnable.java:40) > [transactions-repository-1-2cbrv] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [transactions-repository-1-2cbrv] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [transactions-repository-1-2cbrv] at java.lang.Thread.run(Thread.java:745) > [transactions-repository-1-2cbrv] Caused by: java.lang.ClassCastException: org.infinispan.container.versioning.SimpleClusteredVersion cannot be cast to org.infinispan.container.versioning.NumericVersion > [transactions-repository-1-2cbrv] at org.infinispan.server.hotrod.ClientListenerRegistry$BaseClientEventSender.onCacheEvent(ClientListenerRegistry.java:363) > [transactions-repository-1-2cbrv] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [transactions-repository-1-2cbrv] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > [transactions-repository-1-2cbrv] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [transactions-repository-1-2cbrv] at java.lang.reflect.Method.invoke(Method.java:498) > [transactions-repository-1-2cbrv] at org.infinispan.notifications.impl.AbstractListenerImpl$ListenerInvocationImpl$1.run(AbstractListenerImpl.java:396) > [transactions-repository-1-2cbrv] ... 16 more > [transactions-repository-1-2cbrv] > {code} > This didn't happen in {{CR2}} release, so there must be something that changed since then. I also noticed that this sometimes leads to exceptions in the Hot Rod client. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7682) DistributionManager's cache topology updated in wrong order

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7682?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-7682: ------------------------------------ I agree, there's no "proper order" to update all these topology fields. Initially I wanted to use a single field, but I think I hit some problems in the test suite and went back to having a separate field in {{StateConsumerImpl}}. I'll see if I can merge the {{TriangleOrderManager}} one, too. > DistributionManager's cache topology updated in wrong order > ----------------------------------------------------------- > > Key: ISPN-7682 > URL: https://issues.jboss.org/browse/ISPN-7682 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.CR3 > Reporter: Radim Vansa > Assignee: Dan Berindei > > {{StateTransferInterceptor}} sets command topology according to {{StateTransferManager.getCacheTopology()}} which goes to {{StateConsumerImpl}}, but {{EntryWrappingInterceptor}} routes according to {{DistributionManager.getCacheTopology()}}. {{StateConsumer}}'s topology is set in {{onTopologyUpdate}} before {{DistributionManager}}'s, and therefore a command can have the current topology set, but EWI does not wrap the entry and some assertions in {{BaseDistributionInterceptor.remoteGet}} fails. > This is a regression brought in ISPN-7400. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7682) DistributionManager's cache topology updated in wrong order

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7682?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7682: ------------------------------- Status: Open (was: New) > DistributionManager's cache topology updated in wrong order > ----------------------------------------------------------- > > Key: ISPN-7682 > URL: https://issues.jboss.org/browse/ISPN-7682 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.CR3 > Reporter: Radim Vansa > Assignee: Dan Berindei > > {{StateTransferInterceptor}} sets command topology according to {{StateTransferManager.getCacheTopology()}} which goes to {{StateConsumerImpl}}, but {{EntryWrappingInterceptor}} routes according to {{DistributionManager.getCacheTopology()}}. {{StateConsumer}}'s topology is set in {{onTopologyUpdate}} before {{DistributionManager}}'s, and therefore a command can have the current topology set, but EWI does not wrap the entry and some assertions in {{BaseDistributionInterceptor.remoteGet}} fails. > This is a regression brought in ISPN-7400. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPRK-40) Update to Infinispan 9.0.0.Beta2

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPRK-40?page=com.atlassian.jira.plugin.s... ] Gustavo Fernandes updated ISPRK-40: ----------------------------------- Issue Type: Task (was: Component Upgrade) > Update to Infinispan 9.0.0.Beta2 > -------------------------------- > > Key: ISPRK-40 > URL: https://issues.jboss.org/browse/ISPRK-40 > Project: Infinispan Spark > Issue Type: Task > Affects Versions: 0.4 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 0.5 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPRK-44) Drop support for Scala 2.10

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPRK-44?page=com.atlassian.jira.plugin.s... ] Gustavo Fernandes updated ISPRK-44: ----------------------------------- Issue Type: Task (was: Feature Request) > Drop support for Scala 2.10 > --------------------------- > > Key: ISPRK-44 > URL: https://issues.jboss.org/browse/ISPRK-44 > Project: Infinispan Spark > Issue Type: Task > Components: Build > Affects Versions: 0.4 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 0.5 > > > The next version of Spark will remove Scala 2.10 support -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7691) infinispan.client.hotrod.protocol_version ignored

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-7691: --------------------------------------- Summary: infinispan.client.hotrod.protocol_version ignored Key: ISPN-7691 URL: https://issues.jboss.org/browse/ISPN-7691 Project: Infinispan Issue Type: Bug Reporter: Gustavo Fernandes Setting {{infinispan.client.hotrod.protocol_version}} via properties will not take effect due to a parsing error -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPRK-45) Update to Infinispan 9.0.0.Final

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPRK-45?page=com.atlassian.jira.plugin.s... ] Gustavo Fernandes updated ISPRK-45: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update to Infinispan 9.0.0.Final > -------------------------------- > > Key: ISPRK-45 > URL: https://issues.jboss.org/browse/ISPRK-45 > Project: Infinispan Spark > Issue Type: Component Upgrade > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 0.5 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 March 2017