[JBoss JIRA] (ISPN-6968) Clarify Query DSL error message regarding number format
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-6968?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6968:
----------------------------------
Fix Version/s: 9.1.0.Final
(was: 9.0.0.Final)
> Clarify Query DSL error message regarding number format
> -------------------------------------------------------
>
> Key: ISPN-6968
> URL: https://issues.jboss.org/browse/ISPN-6968
> Project: Infinispan
> Issue Type: Enhancement
> Affects Versions: 8.0.0.Final
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 9.1.0.Final
>
>
> The query:
> {code}
> Query query = queryFactory.from(User.class)
> .select(property("name"), count("age"))
> .having("age").gte(2.3)
> .toBuilder().groupBy("name")
> .build();
> List<Object[]> list = query.list();
> {code}
> will result in an error:
> {code}
> org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=13 returned server error (status=0x85): org.hibernate.hql.ParsingException: ISPN028505: Invalid numeric literal '2.3'
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:343)
> {code}
> This is a bit confusing because it does not clearly state that an integer is expected.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (ISPN-6964) Flag is not included in Javadocs
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-6964?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6964:
----------------------------------
Fix Version/s: 9.1.0.Final
(was: 9.0.0.Final)
> Flag is not included in Javadocs
> --------------------------------
>
> Key: ISPN-6964
> URL: https://issues.jboss.org/browse/ISPN-6964
> Project: Infinispan
> Issue Type: Bug
> Components: Documentation-Core
> Affects Versions: 8.2.4.Final, 9.0.0.Alpha4
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 9.1.0.Final, 8.2.7.Final
>
>
> The AdvancedCache javadocs refer to the Flag enumeration, but this is not included in the javadoc. Also DecoratedCache, which should be an internal implementation detail, is referenced as a public API.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (ISPN-6956) AffinityPartitioner enabled as default partitioner
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-6956?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6956:
----------------------------------
Fix Version/s: 9.1.0.Final
(was: 9.0.0.Final)
> AffinityPartitioner enabled as default partitioner
> --------------------------------------------------
>
> Key: ISPN-6956
> URL: https://issues.jboss.org/browse/ISPN-6956
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Reporter: Sanne Grinovero
> Assignee: Sanne Grinovero
> Fix For: 9.1.0.Final
>
>
> Having the {{org.infinispan.distribution.ch.impl.AffinityPartitioner}} as default enabled {{KeyPartitioner}} will allow people to use the functionality offered by {{org.infinispan.distribution.ch.AffinityTaggedKey}} out of the box, without needing to enable it explicitly in configuration.
> {{AffinityTaggedKey}} is used by Query but not only.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (ISPN-6819) SharedStoreInvalidationDuringRehashTest.testRehashWith[out]Preload random failures
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-6819?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6819:
----------------------------------
Fix Version/s: 9.1.0.Final
(was: 9.0.0.Final)
> SharedStoreInvalidationDuringRehashTest.testRehashWith[out]Preload random failures
> ----------------------------------------------------------------------------------
>
> Key: ISPN-6819
> URL: https://issues.jboss.org/browse/ISPN-6819
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Test Suite - Core
> Affects Versions: 9.0.0.Alpha2, 8.2.4.Final
> Reporter: Dan Berindei
> Priority: Critical
> Labels: testsuite_stability
> Fix For: 9.1.0.Final
>
>
> {noformat}
> java.lang.AssertionError: expected:<0> but was:<3>
> at org.testng.AssertJUnit.fail(AssertJUnit.java:59)
> at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:245)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:252)
> at org.infinispan.distribution.rehash.SharedStoreInvalidationDuringRehashTest.checkContentAndInvalidations(SharedStoreInvalidationDuringRehashTest.java:213)
> at org.infinispan.distribution.rehash.SharedStoreInvalidationDuringRehashTest.doTest(SharedStoreInvalidationDuringRehashTest.java:135)
> at org.infinispan.distribution.rehash.SharedStoreInvalidationDuringRehashTest.testRehashWithoutPreload(SharedStoreInvalidationDuringRehashTest.java:122)
> {noformat}
> http://ci.infinispan.org/project.html?tab=testDetails&testNameId=-7068250...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (ISPN-6766) hot rod client: RemoteCache.removeClient method does not remove the listener from the list after server restart
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-6766?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6766:
----------------------------------
Fix Version/s: 9.1.0.Final
(was: 9.0.0.Final)
> hot rod client: RemoteCache.removeClient method does not remove the listener from the list after server restart
> ---------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-6766
> URL: https://issues.jboss.org/browse/ISPN-6766
> Project: Infinispan
> Issue Type: Bug
> Components: Listeners, Remote Protocols
> Affects Versions: 8.2.1.Final
> Reporter: Eli Z
> Priority: Minor
> Fix For: 9.1.0.Final
>
>
> After registering a client listener in the client and then restarting the infinispan server --> The original listener object can not be removed from the client listener list by using the method RemoteCache.removeClient(Object listener) --> after calling this method and then get all listeners, i still see the old listener in the list.
> By doing a little debug, it seems that in class RemoveClientListenerOperation.execute when trying to remove from the server and a failure status is returned (probably due to the fact the the server after the restart does not know this listener id) the listener is not removed from the list eventually. the line this.listenerNotifier.removeClientListener(listenerId); is not executed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months