February 2016 - infinispan-issues

[JBoss JIRA] (ISPN-6138) Remove type parameter form QueryBuilder and QueryFactory

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-6138: ----------------------------------- Summary: Remove type parameter form QueryBuilder and QueryFactory Key: ISPN-6138 URL: https://issues.jboss.org/browse/ISPN-6138 Project: Infinispan Issue Type: Bug Components: Embedded Querying, Remote Querying Reporter: Adrian Nistor Assignee: Adrian Nistor That parameter has become meaningless after several refactorings. It will always be ```Query```, never a subtype of it, so it can be removed. This will not be backward compatible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6138) Remove type parameter form QueryBuilder and QueryFactory

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6138?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6138: -------------------------------- Status: Open (was: New) > Remove type parameter form QueryBuilder and QueryFactory > -------------------------------------------------------- > > Key: ISPN-6138 > URL: https://issues.jboss.org/browse/ISPN-6138 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > > That parameter has become meaningless after several refactorings. It will always be ```Query```, never a subtype of it, so it can be removed. > This will not be backward compatible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6138) Remove type parameter form QueryBuilder and QueryFactory

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6138?page=com.atlassian.jira.plugin.... ] Work on ISPN-6138 started by Adrian Nistor. ------------------------------------------- > Remove type parameter form QueryBuilder and QueryFactory > -------------------------------------------------------- > > Key: ISPN-6138 > URL: https://issues.jboss.org/browse/ISPN-6138 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > > That parameter has become meaningless after several refactorings. It will always be ```Query```, never a subtype of it, so it can be removed. > This will not be backward compatible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6128) Expose ProtoBuf Manager through DMR

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6128?page=com.atlassian.jira.plugin.... ] Work on ISPN-6128 started by Adrian Nistor. ------------------------------------------- > Expose ProtoBuf Manager through DMR > ----------------------------------- > > Key: ISPN-6128 > URL: https://issues.jboss.org/browse/ISPN-6128 > Project: Infinispan > Issue Type: Task > Components: Remote Querying, Server > Reporter: Tristan Tarrant > Assignee: Adrian Nistor > Fix For: 8.2.0.Final > > > The ProtoBuf Manager should be exposed through the DMR as a child resource under cache-container nodes. The resource should expose a number of operations to list, get, set, remove installed schemas. > Example: > .../cache-container=container/protobuf-schemas=PROTOBUF-SCHEMAS > :list-schemas() > :get-schema(name=myschema) > :remove-schema(name=myschema) > :set-schema(name=myschema, schema-source=...) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6128) Expose ProtoBuf Manager through DMR

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6128?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6128: -------------------------------- Status: Open (was: New) > Expose ProtoBuf Manager through DMR > ----------------------------------- > > Key: ISPN-6128 > URL: https://issues.jboss.org/browse/ISPN-6128 > Project: Infinispan > Issue Type: Task > Components: Remote Querying, Server > Reporter: Tristan Tarrant > Assignee: Adrian Nistor > Fix For: 8.2.0.Final > > > The ProtoBuf Manager should be exposed through the DMR as a child resource under cache-container nodes. The resource should expose a number of operations to list, get, set, remove installed schemas. > Example: > .../cache-container=container/protobuf-schemas=PROTOBUF-SCHEMAS > :list-schemas() > :get-schema(name=myschema) > :remove-schema(name=myschema) > :set-schema(name=myschema, schema-source=...) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6135) ScriptMetadataTest.testBrokenParameters fails due to logging id changes

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6135?page=com.atlassian.jira.plugin.... ] Adrian Nistor closed ISPN-6135. ------------------------------- Fix Version/s: (was: 8.2.0.Final) Resolution: Duplicate Issue > ScriptMetadataTest.testBrokenParameters fails due to logging id changes > ----------------------------------------------------------------------- > > Key: ISPN-6135 > URL: https://issues.jboss.org/browse/ISPN-6135 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.2.0.Beta1 > Reporter: Adrian Nistor > Assignee: Tristan Tarrant > > See http://ci.infinispan.org/viewLog.html?buildId=34825&tab=buildResultsDiv&b... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 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: -------------------------------- Fix Version/s: (was: 8.2.0.CR1) > 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 (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6051) ClusterExpirationManager missing locking

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6051?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-6051: ------------------------------------- Unfortunately we can't create the command in the DataContainer lock on a non owner node as this would cause a deadlock issue. If we do this in the data container compute and another concurrent write occurs on the same key the primary will send a write command to the backup owner and then it will never be able to acquire the data container lock. And the remote node will not be able to acquire the Infinispan lock on the primary node for that key. Unfortunately this can't be fixed this way. > ClusterExpirationManager missing locking > ---------------------------------------- > > Key: ISPN-6051 > URL: https://issues.jboss.org/browse/ISPN-6051 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.1.0.Final > Reporter: Dan Berindei > Assignee: William Burns > Fix For: 8.2.0.CR1 > > > Because {{ClusterExpirationManager.handleLifespanExpired()}} doesn't lock the entry and the value is actually read in the async thread, the created {{RemoveExpiredCommand}} sometimes uses a newer value written by another thread. > Could be fixed by using {{DataContainer.compute()}} to check expiration and create the {{RemoveExpirationCommand}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6137) ScriptMetadataTest.testBrokenParameters fails since the logging range changes

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6137?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6137: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3974 > ScriptMetadataTest.testBrokenParameters fails since the logging range changes > ----------------------------------------------------------------------------- > > Key: ISPN-6137 > URL: https://issues.jboss.org/browse/ISPN-6137 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 8.2.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.2.0.CR1 > > > The ISPN-6123 fix changed the logging ids for the scripting module, breaking `ScriptMetadataTest.testBrokenParameters`: > {noformat} > The exception was thrown with the wrong message: expected "^ISPN021011.*" but got "ISPN026011: Script parameters must be declared using the array notation, e.g. [a,b,c]" > at org.testng.internal.Invoker.handleInvocationResults(Invoker.java:1481) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:754) > 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) > Caused by: java.lang.IllegalArgumentException: ISPN026011: Script parameters must be declared using the array notation, e.g. [a,b,c] > at org.infinispan.scripting.impl.ScriptMetadataParser.unarray(ScriptMetadataParser.java:99) > at org.infinispan.scripting.impl.ScriptMetadataParser.parse(ScriptMetadataParser.java:56) > at org.infinispan.scripting.ScriptMetadataTest.testBrokenParameters(ScriptMetadataTest.java:63) > 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) > ... 14 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6137) ScriptMetadataTest.testBrokenParameters fails since the logging range changes

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6137?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6137: ------------------------------- Status: Open (was: New) > ScriptMetadataTest.testBrokenParameters fails since the logging range changes > ----------------------------------------------------------------------------- > > Key: ISPN-6137 > URL: https://issues.jboss.org/browse/ISPN-6137 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 8.2.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.2.0.CR1 > > > The ISPN-6123 fix changed the logging ids for the scripting module, breaking `ScriptMetadataTest.testBrokenParameters`: > {noformat} > The exception was thrown with the wrong message: expected "^ISPN021011.*" but got "ISPN026011: Script parameters must be declared using the array notation, e.g. [a,b,c]" > at org.testng.internal.Invoker.handleInvocationResults(Invoker.java:1481) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:754) > 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) > Caused by: java.lang.IllegalArgumentException: ISPN026011: Script parameters must be declared using the array notation, e.g. [a,b,c] > at org.infinispan.scripting.impl.ScriptMetadataParser.unarray(ScriptMetadataParser.java:99) > at org.infinispan.scripting.impl.ScriptMetadataParser.parse(ScriptMetadataParser.java:56) > at org.infinispan.scripting.ScriptMetadataTest.testBrokenParameters(ScriptMetadataTest.java:63) > 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) > ... 14 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2016