April 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5665) Query should not rely on the results of return values of write commands

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-5665?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-5665: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > Query should not rely on the results of return values of write commands > ----------------------------------------------------------------------- > > Key: ISPN-5665 > URL: https://issues.jboss.org/browse/ISPN-5665 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 8.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Gustavo Fernandes > Fix For: 9.0.0.Alpha2 > > > The query interceptor relies on the return value of the write commands to know the previous value of the modified entries. This is not correct, because some write commands do not return the previous value, e.g. {{remove(key, value)}}, {{replace(key, oldValue, newValue)}}, and {{putAll(map)}}. > The query interceptor should instead look up the previous values in the invocation context, and also force the loading of old values in the invocation context if the command doesn't do it explicitly (e.g. {{putAll(map)}}, or {{put(k, v)}} with the {{IGNORE_RETURN_VALUES}} flag). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5892) XML configuration should include number of segments for replicated caches

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-5892?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-5892: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > XML configuration should include number of segments for replicated caches > ------------------------------------------------------------------------- > > Key: ISPN-5892 > URL: https://issues.jboss.org/browse/ISPN-5892 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 8.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Alpha2 > > > The primary owner of a key is determined based on the segment, so for remote caches it's good to increase the number of segments when there are many nodes in the cluster. Groups configuration may be useful as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5862) Add version number to deprecated comments

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-5862?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-5862: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > Add version number to deprecated comments > ----------------------------------------- > > Key: ISPN-5862 > URL: https://issues.jboss.org/browse/ISPN-5862 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Affects Versions: 8.1.0.Alpha1 > Reporter: Dan Berindei > Fix For: 9.0.0.Alpha2 > > > It should be possible to remove deprecated classes and methods after one major version cycle, but it's not always obvious when the API was deprecated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5853) Add Hawkular subsytem to server distribution

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-5853?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-5853: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > Add Hawkular subsytem to server distribution > -------------------------------------------- > > Key: ISPN-5853 > URL: https://issues.jboss.org/browse/ISPN-5853 > Project: Infinispan > Issue Type: Task > Components: JMX, reporting and management, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Alpha2 > > > https://github.com/hawkular/hawkular-agent/blob/master/hawkular-wildfly-a... > <storage-adapter type="HAWKULAR" username="jdoe" password="password" url="http://${jboss.bind.address:127.0.0.1}:${jboss.http.port:8080}" /> > Use bindings. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5849) AutoCloseable return from adding listeners can be clunky to use

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-5849?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-5849: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > AutoCloseable return from adding listeners can be clunky to use > --------------------------------------------------------------- > > Key: ISPN-5849 > URL: https://issues.jboss.org/browse/ISPN-5849 > Project: Infinispan > Issue Type: Sub-task > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.Alpha2 > > > On one side, to use it as a try-with-resource, you need to declare it right in the {{try()}}; > {code} > try(AutoCloseable handler = writeOnlyMap.listeners().onWrite(written -> > System.out.printf("Written (via onWrite): %s%n", written.get()))) { > Map<String, String> entries = new HashMap<>(); > entries.put("key1", "value1"); > entries.put("key2", "value2"); > writeOnlyMap.evalMany(entries, (v, writeView) -> writeView.set(v)) > .get(); // Wait for completable future > } > {code} > So it's usability is mostly designed for unit tests since listeners tend to be set and removed at a later stage. IOW, listeners are not generally a short-lived object. > The other aspect that is clunky to use is the fact that AutoCloseable's close() throws Exception, which again makes it ackward to use for example if lambdas. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5803) Custom Key Results in ClassCastException in CacheLoader

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-5803?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-5803: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > Custom Key Results in ClassCastException in CacheLoader > ------------------------------------------------------- > > Key: ISPN-5803 > URL: https://issues.jboss.org/browse/ISPN-5803 > Project: Infinispan > Issue Type: Bug > Components: JCache > Affects Versions: 8.0.1.Final > Reporter: Dan Siviter > Assignee: Galder Zamarreño > Fix For: 9.0.0.Alpha2 > > > If a a JCache is created using a read-through {{javax.cache.integration.CacheLoader}} using a custom Serializable key (in this case {{acme.MyCache$MyKey}}) a {{ClassCastException}} is thrown when trying to pass the key value of {{org.infinispan.marshall.core.MarshalledValue}} instead of {{MarshalledValue#get()}} into the {{CacheLoader}} instance. > {code} > java.lang.ClassCastException: org.infinispan.marshall.core.MarshalledValue cannot be cast to acme.MyCache$MyKey > at acme.MyCache$2.load(MyCache.java:1) [my-app-1.0.0-SNAPSHOT.jar:] > at org.infinispan.jcache.embedded.JCacheLoaderAdapter.loadKey(JCacheLoaderAdapter.java:65) [infinispan-jcache-8.0.1.Final.jar:8.0.1.Final] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5794) Hot Rod should use functional map to do version-based replace

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-5794?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-5794: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > Hot Rod should use functional map to do version-based replace > ------------------------------------------------------------- > > Key: ISPN-5794 > URL: https://issues.jboss.org/browse/ISPN-5794 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.Alpha2 > > > Hot Rod should do version-based replace using the functional map API so that atomicity can be guaranteed and avoid odd behaviour like ISPN-4972 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5793) Expose massindexer status and progress over mbean/dmr

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-5793?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-5793: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > Expose massindexer status and progress over mbean/dmr > ----------------------------------------------------- > > Key: ISPN-5793 > URL: https://issues.jboss.org/browse/ISPN-5793 > Project: Infinispan > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Gustavo Fernandes > Fix For: 9.0.0.Alpha2 > > > It would be useful for the console/cli to expose the ongoing status/progress of any indexing happening on a cache. This would need to happen both on the massIndexer Mbean and on the server dmr > https://rawgit.com/infinispan/infinispan-console-mockup/master/cache-cont... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6011) ClassCastException in CDI generated keys for JCache

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-6011?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-6011: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > ClassCastException in CDI generated keys for JCache > --------------------------------------------------- > > Key: ISPN-6011 > URL: https://issues.jboss.org/browse/ISPN-6011 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.CR1, 8.0.2.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.Alpha2 > > > When using JCache-annotations the DefaultCacheKeyGenerator exclusively looks at parameter values to form the cache key. Therefore it will be very likely that collissions occur (resulting in difficult to find ClassCastExceptions). The provided patch uses the method- and class names as additionally values to make the cache key more unique. > Might also add that I am aware that by spec this should not be an issue when no cachename is given (as it should generate a cache using the class-name), but when a cache name is given collissions may occur. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6015) Query DSL should support groupBy for multi-valued properties

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-6015?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-6015: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > Query DSL should support groupBy for multi-valued properties > ------------------------------------------------------------ > > Key: ISPN-6015 > URL: https://issues.jboss.org/browse/ISPN-6015 > Project: Infinispan > Issue Type: Feature Request > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha2 > > > If a groupBy property is multivalued the entity will belong to multiple groups, one for each distinct value. > Current implementation in 8.0.x and 8.1.x does not allow this and instead of providing invalid results grouping by multivalued property was disallowed (see ISPN-6008). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 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 April 2016