[JBoss JIRA] (ISPN-5751) Support for Query based filters in the Remote iterator
by Gustavo Fernandes (JIRA)
Gustavo Fernandes created ISPN-5751:
---------------------------------------
Summary: Support for Query based filters in the Remote iterator
Key: ISPN-5751
URL: https://issues.jboss.org/browse/ISPN-5751
Project: Infinispan
Issue Type: Enhancement
Components: Remote Querying, Server
Affects Versions: 8.0.1.Final
Reporter: Gustavo Fernandes
Remote {{cache.retrieveEntries}} currently allows the usage of a server deployed filters in order to retrieve custom filtered/converted entries. A Query based filter should be also supported for more flexibility.
Primary consumers are Spark and Hadoop connectors
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (ISPN-5497) MetadataAPIDefaultExpiryTest.testDefaultLifespanReplaceWithOldValue and MetadataAPIDefaultExpiryTest.testDefaultLifespanPutIfAbsent fail randomly
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-5497?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-5497:
-------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/3709
> MetadataAPIDefaultExpiryTest.testDefaultLifespanReplaceWithOldValue and MetadataAPIDefaultExpiryTest.testDefaultLifespanPutIfAbsent fail randomly
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-5497
> URL: https://issues.jboss.org/browse/ISPN-5497
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 7.2.1.Final
> Reporter: Roman Macor
> Assignee: Dan Berindei
>
> MetadataAPIDefaultExpiryTest.testDefaultLifespanPutIfAbsent and MetadataAPIDefaultExpiryTest.testDefaultLifespanReplaceWithOldValue fail randomly with assertion error
> org.infinispan.api.MetadataAPIDefaultExpiryTest.testDefaultLifespanReplaceWithOldValue
> Error Message
> expected:<v11> but was:<null>
> Stacktrace
> java.lang.AssertionError: expected:<v11> but was:<null>
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:101)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:108)
> at org.infinispan.api.MetadataAPIDefaultExpiryTest.expectCachedThenExpired(MetadataAPIDefaultExpiryTest.java:85)
> at org.infinispan.api.MetadataAPIDefaultExpiryTest.testDefaultLifespanReplaceWithOldValue(MetadataAPIDefaultExpiryTest.java:49)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
> at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> at org.testng.TestRunner.privateRun(TestRunner.java:767)
> at org.testng.TestRunner.run(TestRunner.java:617)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> at org.testng.SuiteRunner.access$000(SuiteRunner.java:37)
> at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368)
> at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> org.infinispan.api.MetadataAPIDefaultExpiryTest.testDefaultLifespanPutIfAbsent
> Error Message
> expected:<v1> but was:<null>
> Stacktrace
> java.lang.AssertionError: expected:<v1> but was:<null>
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:101)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:108)
> at org.infinispan.api.MetadataAPIDefaultExpiryTest.expectCachedThenExpired(MetadataAPIDefaultExpiryTest.java:85)
> at org.infinispan.api.MetadataAPIDefaultExpiryTest.testDefaultLifespanPutIfAbsent(MetadataAPIDefaultExpiryTest.java:57)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
> at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> at org.testng.TestRunner.privateRun(TestRunner.java:767)
> at org.testng.TestRunner.run(TestRunner.java:617)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> at org.testng.SuiteRunner.access$000(SuiteRunner.java:37)
> at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368)
> at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (ISPN-5545) Make lazy near caching more selective
by Enrico Olivelli (JIRA)
[ https://issues.jboss.org/browse/ISPN-5545?page=com.atlassian.jira.plugin.... ]
Enrico Olivelli commented on ISPN-5545:
---------------------------------------
is there any interest on this issue from other users ?
actually on a large cluster (100 nearcache hotrod nodes) the nearcache floods the network
> Make lazy near caching more selective
> -------------------------------------
>
> Key: ISPN-5545
> URL: https://issues.jboss.org/browse/ISPN-5545
> Project: Infinispan
> Issue Type: Enhancement
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
>
> In the current form, when lazy near caching is enabled, the server sends invalidation messages for any key that has been created, modified or removed.
> This is suboptimal for a couple of reasons:
> 1. First of all, a near cache might only interested in receiving invalidation events for those keys that are currently stored in the near cache. If the near cache is small subset of the entire cache, having such option would vastly reduce the number of events sent to clients. So, there needs to be a way to be able to narrow the events sent from the server to this subset of keys.
> 2. Lazy near caches do not care about created events. If an entry is present in the near cache, it has already been created, so it's only interested in modified and removed events. There needs to be a way to narrow this down too.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (ISPN-5667) Unify isExpired for time and entries
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-5667?page=com.atlassian.jira.plugin.... ]
Dan Berindei commented on ISPN-5667:
------------------------------------
[~william.burns] overflow is not a problem, because ExpiryHelper only deals with wall-clock time (in milliseconds).
I would prefer changing {{ExpiryHelper}} to use {{>=}}. On the other hand, because {{ExpiryHelper.isExpiredMortal()}} works with {{System.currentTimeMillis()}} and {{DefaultTimeService.isTimeExpired()}} works with {{System.nanoTime()}}, I don't think it's possible to get them to agree all the time.
> Unify isExpired for time and entries
> ------------------------------------
>
> Key: ISPN-5667
> URL: https://issues.jboss.org/browse/ISPN-5667
> Project: Infinispan
> Issue Type: Bug
> Reporter: Radim Vansa
>
> {{DefaultTimeService.isTimeExpired()}} is implemented using non-strict comparison:
> {code}
> time() - endTime >= 0
> {code}
> while expiration of entries in {{ExpiryHelper}} uses strict one:
> {code}
> now > created + lifespan
> {code}
> I don't know which one should be the correct one, probably fixing this in TimeService will cause less trouble.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months