February 2018 - infinispan-issues

[JBoss JIRA] (ISPN-6162) Drop Query.getResultSize() method

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6162?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6162: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Drop Query.getResultSize() method > --------------------------------- > > Key: ISPN-6162 > URL: https://issues.jboss.org/browse/ISPN-6162 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, Remote Querying > Reporter: Tristan Tarrant > Assignee: Adrian Nistor > Fix For: 9.3.0.Final > > > Do we keep org.infinispan.query.dsl.Query.getResultSize? Does it return int or long? Return -1 if actual figure unknown/hard to compute? Result size might be non-trivial for non-indexed or hybrid case and will require full scan even for queries with limit. Deprecate it now, remove in ispn 9. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6161) Indexes should be created only for annotated message types

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6161?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6161: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Indexes should be created only for annotated message types > ---------------------------------------------------------- > > Key: ISPN-6161 > URL: https://issues.jboss.org/browse/ISPN-6161 > Project: Infinispan > Issue Type: Task > Components: Remote Querying > Reporter: Tristan Tarrant > Assignee: Adrian Nistor > Fix For: 9.3.0.Final > > > Modify behaviour of indexing for protobuf entities: Current behaviour is: if the message types is not annotated then we index all its fields; if some fields are annotated then index those fields only. New behaviour: index only the annotated fields. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6158) Move interceptors to private package

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6158?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6158: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Move interceptors to private package > ------------------------------------ > > Key: ISPN-6158 > URL: https://issues.jboss.org/browse/ISPN-6158 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Tristan Tarrant > Assignee: Dan Berindei > Fix For: 9.3.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6155) Drop the RHQ plugin

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6155?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6155: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Drop the RHQ plugin > ------------------- > > Key: ISPN-6155 > URL: https://issues.jboss.org/browse/ISPN-6155 > Project: Infinispan > Issue Type: Task > Components: JMX, reporting and management > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.3.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6154) Move GridFS to its own repository

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6154?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6154: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Move GridFS to its own repository > --------------------------------- > > Key: ISPN-6154 > URL: https://issues.jboss.org/browse/ISPN-6154 > Project: Infinispan > Issue Type: Task > Components: Demos and Tutorials > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.3.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6153) Move demos to their own source repository

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6153?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6153: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Move demos to their own source repository > ----------------------------------------- > > Key: ISPN-6153 > URL: https://issues.jboss.org/browse/ISPN-6153 > Project: Infinispan > Issue Type: Task > Components: Demos and Tutorials > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.3.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6094) Use security actions to read system properties for configuration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6094?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6094: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Use security actions to read system properties for configuration > ---------------------------------------------------------------- > > Key: ISPN-6094 > URL: https://issues.jboss.org/browse/ISPN-6094 > Project: Infinispan > Issue Type: Task > Components: Core, Embedded Querying > Affects Versions: 8.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.3.0.Final > > > Infinispan uses system properties for out-of-band settings that weren't deemed important enough to have a proper configuration attribute: > * infinispan.arrays.debug > * infinispan.unsafe.force_multicast > * infinispan.compat (obsolete?) > * infinispan.debugDependencies > * infinispan.stagger.delay (introduced with ISPN-825) > * org.infinispan.query.indexmanager.LockAcquiringBackend.MAX_QUEUE_SIZE > We should use a {{SecurityActions}} class to access these properties instead of {{Boolean.getBoolean()}} and {{Integer.getInteger()}}. We should also document these system properties, and evaluate moving them to the proper configuration. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6084) Continuous query should reject queries with orderBy

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6084?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6084: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Continuous query should reject queries with orderBy > --------------------------------------------------- > > Key: ISPN-6084 > URL: https://issues.jboss.org/browse/ISPN-6084 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 8.1.0.Final, 8.0.2.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Minor > Fix For: 9.3.0.Final > > > Current behaviour it that orderBy is silently ignored. Disallowing this and throwing an exception would be preferable. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6336) NonIndexedClusteredDummyInMemoryStoreQueryDslConditionsTest random failures

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6336?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6336: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > NonIndexedClusteredDummyInMemoryStoreQueryDslConditionsTest random failures > --------------------------------------------------------------------------- > > Key: ISPN-6336 > URL: https://issues.jboss.org/browse/ISPN-6336 > Project: Infinispan > Issue Type: Bug > Reporter: Gustavo Fernandes > Assignee: Adrian Nistor > Labels: testsuite_stability > Fix For: 9.3.0.Final > > > Picked this failure when running the query testsuite in loop. It's somehow hard to reproduce. > The presence of the Byteman test runner in the stacktrace looks suspicious, since it is not supposed to run this test. > {code} > Tests run: 2907, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 51.21 sec <<< FAILURE! - in TestSuite > testSampleDomainQuery16(org.infinispan.query.dsl.embedded.NonIndexedClusteredDummyInMemoryStoreQueryDslConditionsTest) Time elapsed: 0.01 sec <<< FAILURE! > java.lang.AssertionError: expected:<50> but was:<0> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at org.infinispan.query.dsl.embedded.QueryDslConditionsTest.testSampleDomainQuery16(QueryDslConditionsTest.java:1366) > 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.MethodInvocationHelper$1.runTestMethod(MethodInvocationHelper.java:200) > at org.jboss.byteman.contrib.bmunit.BMNGAbstractRunner.run(BMNGAbstractRunner.java:58) > at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.testng.internal.MethodInvocationHelper.invokeHookable(MethodInvocationHelper.java:212) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:707) > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6294) Query DSL should allow easy 'continuation' to assist with creating dynamic queries

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6294?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6294: ---------------------------------- Fix Version/s: 9.3.0.Final (was: 9.2.0.Final) > Query DSL should allow easy 'continuation' to assist with creating dynamic queries > ---------------------------------------------------------------------------------- > > Key: ISPN-6294 > URL: https://issues.jboss.org/browse/ISPN-6294 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Adrian Nistor > Fix For: 9.3.0.Final > > > Conditional chaining of DSL conditions is cumbersome, as shown here: https://github.com/infinispan/infinispan/blob/af7f38ba1cf538be6b08d7b895f... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2018