May 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8415) Func eval: pass arbitrary value

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-8415?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-8415: ------------------------------ Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan/pull/5796 > Func eval: pass arbitrary value > ------------------------------- > > Key: ISPN-8415 > URL: https://issues.jboss.org/browse/ISPN-8415 > Project: Infinispan > Issue Type: Enhancement > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.2.0.Final > > > The current API for eval methods and commands with values are limited to passing an argument of the same type as the stored value. This is limiting, sometimes we'd prefer to pass just a delta (of different type). > We'll keep a limitation that the delta needs to be encoded/decoded by the value decoder. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8415) Func eval: pass arbitrary value

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-8415?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-8415: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Func eval: pass arbitrary value > ------------------------------- > > Key: ISPN-8415 > URL: https://issues.jboss.org/browse/ISPN-8415 > Project: Infinispan > Issue Type: Enhancement > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.2.0.Final > > > The current API for eval methods and commands with values are limited to passing an argument of the same type as the stored value. This is limiting, sometimes we'd prefer to pass just a delta (of different type). > We'll keep a limitation that the delta needs to be encoded/decoded by the value decoder. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8415) Func eval: pass arbitrary value

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-8415?page=com.atlassian.jira.plugin.... ] Radim Vansa closed ISPN-8415. ----------------------------- > Func eval: pass arbitrary value > ------------------------------- > > Key: ISPN-8415 > URL: https://issues.jboss.org/browse/ISPN-8415 > Project: Infinispan > Issue Type: Enhancement > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.2.0.Final > > > The current API for eval methods and commands with values are limited to passing an argument of the same type as the stored value. This is limiting, sometimes we'd prefer to pass just a delta (of different type). > We'll keep a limitation that the delta needs to be encoded/decoded by the value decoder. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8415) Func eval: pass arbitrary value

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-8415?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-8415: ------------------------------ Fix Version/s: 9.2.0.Final > Func eval: pass arbitrary value > ------------------------------- > > Key: ISPN-8415 > URL: https://issues.jboss.org/browse/ISPN-8415 > Project: Infinispan > Issue Type: Enhancement > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.2.0.Final > > > The current API for eval methods and commands with values are limited to passing an argument of the same type as the stored value. This is limiting, sometimes we'd prefer to pass just a delta (of different type). > We'll keep a limitation that the delta needs to be encoded/decoded by the value decoder. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8415) Func eval: pass arbitrary value

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-8415?page=com.atlassian.jira.plugin.... ] Radim Vansa closed ISPN-8415. ----------------------------- Resolution: Done > Func eval: pass arbitrary value > ------------------------------- > > Key: ISPN-8415 > URL: https://issues.jboss.org/browse/ISPN-8415 > Project: Infinispan > Issue Type: Enhancement > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.2.0.Final > > > The current API for eval methods and commands with values are limited to passing an argument of the same type as the stored value. This is limiting, sometimes we'd prefer to pass just a delta (of different type). > We'll keep a limitation that the delta needs to be encoded/decoded by the value decoder. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6903) SingleFileStoreStressTest.testFileTruncation fails

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-6903?page=com.atlassian.jira.plugin.... ] Radim Vansa closed ISPN-6903. ----------------------------- Resolution: Out of Date Reopen if CI hit this again. > SingleFileStoreStressTest.testFileTruncation fails > -------------------------------------------------- > > Key: ISPN-6903 > URL: https://issues.jboss.org/browse/ISPN-6903 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Sebastian Łaskawiec > Assignee: Radim Vansa > Priority: Critical > > http://ci.infinispan.org/viewLog.html?buildId=41261&tab=buildResultsDiv&b... > {code} > java.lang.AssertionError: > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:24) > at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:33) > at org.infinispan.persistence.file.SingleFileStoreStressTest.testFileTruncation(SingleFileStoreStressTest.java:272) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > 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:348) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:38) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:382) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9189) ExceptionEvictionTest test failure causes testng to panic

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9189?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9189: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.3.0.CR1 Resolution: Done > ExceptionEvictionTest test failure causes testng to panic > --------------------------------------------------------- > > Key: ISPN-9189 > URL: https://issues.jboss.org/browse/ISPN-9189 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.3.0.CR1 > Reporter: Gustavo Fernandes > Assignee: Dan Berindei > Fix For: 9.3.0.CR1 > > > A single test failure is apparently causing 300+ cascade failures due to cleanup issues on testng. The first logged failure is: > {noformat} > ERROR] clearContent(org.infinispan.eviction.impl.ExceptionEvictionTest) Time elapsed: 0.022 s <<< FAILURE! > java.lang.AssertionError: expected:<0> but was:<1> > 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:170) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:177) > at org.infinispan.eviction.impl.ExceptionEvictionTest.clearContent(ExceptionEvictionTest.java:197) > {noformat} > Followed by 300+ occcurences of: > {noformat} > [ERROR] testExceptionOnInsert[REPL_SYNC, nodeCount=3, storageType=OBJECT, optimisticTransaction=false](org.infinispan.eviction.impl.ExceptionEvictionTest) Time elapsed: 0.001 s <<< FAILURE! > java.lang.NullPointerException > at org.infinispan.commons.test.RunningTestsRegistry.unregisterThreadWithTest(RunningTestsRegistry.java:39) > at org.infinispan.commons.test.TestNGTestListener.onConfigurationFailure(TestNGTestListener.java:142) > at org.testng.internal.Invoker.runConfigurationListeners(Invoker.java:1659) > at org.testng.internal.Invoker.handleConfigurationFailure(Invoker.java:299) > at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:237) > {noformat} > The related build is https://ci.infinispan.org/job/Infinispan/job/master/625/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9193) CollectionMapper forEach should delegate to actualCollection

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9193?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9193: -------------------------------- Status: Open (was: New) > CollectionMapper forEach should delegate to actualCollection > ------------------------------------------------------------ > > Key: ISPN-9193 > URL: https://issues.jboss.org/browse/ISPN-9193 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 9.3.0.CR1 > > > CollectionMapper currently delegates forEach method to the stream instead of the underlying collection. This can cause issues since stream serializes the function across to be executed on all nodes. This should instead delegate to the actualCollection to allow for local operation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9193) CollectionMapper forEach should delegate to actualCollection

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9193?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9193: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6000 > CollectionMapper forEach should delegate to actualCollection > ------------------------------------------------------------ > > Key: ISPN-9193 > URL: https://issues.jboss.org/browse/ISPN-9193 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 9.3.0.CR1 > > > CollectionMapper currently delegates forEach method to the stream instead of the underlying collection. This can cause issues since stream serializes the function across to be executed on all nodes. This should instead delegate to the actualCollection to allow for local operation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5451) Data Container Segment Striping

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5451?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5451: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) > Data Container Segment Striping > ------------------------------- > > Key: ISPN-5451 > URL: https://issues.jboss.org/browse/ISPN-5451 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: William Burns > Assignee: William Burns > > Today each node owns a given number of segments at a time. There are many operations that are only concerned with entries of a given segment. Unfortunately this means that we must iterate over the entire contents of the cache to find only the entries that match given segments. Note this JIRA is only for the in memory data container. The cache store requires additional work and should be done separately as it may involve reworking many more areas of the code base. > # State Transfer entry removal (this removes all entries of given segments) > # Entry retrieval (if we could iterate by segment instead of over all values we could complete segments sooner which would reduce how much memory a client must hold) > # Indexing may want to index by segment at some point as well -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 May 2018