[JBoss JIRA] (ISPN-4088) Modify signature of Query/CacheQuery.getResultSize() and related offset/pagination methods to return long
by Adrian Nistor (JIRA)
Adrian Nistor created ISPN-4088:
-----------------------------------
Summary: Modify signature of Query/CacheQuery.getResultSize() and related offset/pagination methods to return long
Key: ISPN-4088
URL: https://issues.jboss.org/browse/ISPN-4088
Project: Infinispan
Issue Type: Feature Request
Components: Embedded Querying, Remote Querying
Affects Versions: 6.0.0.Final
Reporter: Adrian Nistor
Assignee: Adrian Nistor
Fix For: 7.0.0.Final
The method exists in both new DSL and the classic query api.
It should be clarified whether this method and the related pagination methods should use int or long for specifying offsets within the data, also should decide if the total number of results / results per page is a long or an int - and update all involved method signatures to have a unitary treatment of this issue.
It appears that recent Lucene versions can offer the number of results as long, while older ones offer it as int (should be verified).
This issue was raised in a github conversation here: https://github.com/infinispan/infinispan/pull/2410
--
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
10 years, 10 months
[JBoss JIRA] (ISPN-3944) DistSyncL1RepeatableReadFuncTest.testNoEntryInL1GetWithConcurrentReplace random failures
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-3944?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated ISPN-3944:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1074517
> DistSyncL1RepeatableReadFuncTest.testNoEntryInL1GetWithConcurrentReplace random failures
> ----------------------------------------------------------------------------------------
>
> Key: ISPN-3944
> URL: https://issues.jboss.org/browse/ISPN-3944
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Test Suite - Core
> Affects Versions: 6.0.1.Final
> Reporter: Dan Berindei
> Assignee: William Burns
> Labels: testsuite_stability
> Fix For: 7.0.0.Alpha1, 7.0.0.Final
>
> Attachments: dsl1rrft.log.gz
>
>
> Random failure in DistSyncL1RepeatableReadFuncTest>DistSyncL1FuncTest.testNoEntryInL1GetWithConcurrentReplace:
> {noformat}
> 00:23:34,658 ERROR (testng-DistSyncL1RepeatableReadFuncTest:) [UnitTestTestNGListener] Test testNoEntryInL1GetWithConcurrentReplace(org.infinispan.distribution.DistSyncL1RepeatableReadFuncTest) failed.
> java.lang.AssertionError: Entry for key [key-to-the-cache] should be in L1 on cache at [NodeA-57647]!
> at org.infinispan.distribution.DistributionTestHelper.assertIsInL1(DistributionTestHelper.java:31)
> at org.infinispan.distribution.BaseDistFunctionalTest.assertIsInL1(BaseDistFunctionalTest.java:183)
> at org.infinispan.distribution.DistSyncL1FuncTest.testNoEntryInL1GetWithConcurrentReplace(DistSyncL1FuncTest.java:193)
> {noformat}
--
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
10 years, 10 months
[JBoss JIRA] (ISPN-4087) MBean registration logging should be at lower level
by Tristan Tarrant (JIRA)
Tristan Tarrant created ISPN-4087:
-------------------------------------
Summary: MBean registration logging should be at lower level
Key: ISPN-4087
URL: https://issues.jboss.org/browse/ISPN-4087
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 7.0.0.Alpha1
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Priority: Trivial
Fix For: 7.0.0.Final
Whenever the MBeans are registered, an INFO log is printed which is especially annoying in the server startup. This is an internal detail and does not deserve to be INFO
--
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
10 years, 10 months