August 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5435) Add annotation attribute to allow for listener to specify whether it receives pre, post or all events

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5435?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5435: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1252429|https://bugzilla.redhat.com/show_bug.cgi?id=1252429] from POST to MODIFIED > Add annotation attribute to allow for listener to specify whether it receives pre, post or all events > ----------------------------------------------------------------------------------------------------- > > Key: ISPN-5435 > URL: https://issues.jboss.org/browse/ISPN-5435 > Project: Infinispan > Issue Type: Enhancement > Components: Listeners > Affects Versions: 7.1.1.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 7.2.0.Final > > > It would be nice to have a way for a listener to specify if it has to listen to all pre and post events. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5390) QueryCache should use the internal cache registry

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5390?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5390: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1252429|https://bugzilla.redhat.com/show_bug.cgi?id=1252429] from POST to MODIFIED > QueryCache should use the internal cache registry > ------------------------------------------------- > > Key: ISPN-5390 > URL: https://issues.jboss.org/browse/ISPN-5390 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 7.2.0.Beta2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5678) org.infinispan.functional javadocs not appearing

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5678?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5678: ----------------------------------- Status: Open (was: New) > org.infinispan.functional javadocs not appearing > ------------------------------------------------ > > Key: ISPN-5678 > URL: https://issues.jboss.org/browse/ISPN-5678 > Project: Infinispan > Issue Type: Sub-task > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.0.0.CR1 > > > org.infinispan.functional javadocs missing in beta3 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5678) org.infinispan.functional javadocs not appearing

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5678?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5678: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3651 > org.infinispan.functional javadocs not appearing > ------------------------------------------------ > > Key: ISPN-5678 > URL: https://issues.jboss.org/browse/ISPN-5678 > Project: Infinispan > Issue Type: Sub-task > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.0.0.CR1 > > > org.infinispan.functional javadocs missing in beta3 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5678) org.infinispan.functional javadocs not appearing

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-5678: -------------------------------------- Summary: org.infinispan.functional javadocs not appearing Key: ISPN-5678 URL: https://issues.jboss.org/browse/ISPN-5678 Project: Infinispan Issue Type: Sub-task Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 8.0.0.CR1 org.infinispan.functional javadocs missing in beta3 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5677) HR putIfAbsentAsync not enforcing withFlags(Flag.FORCE_RETURN_VALUE)

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5677?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5677: ----------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/3650 > HR putIfAbsentAsync not enforcing withFlags(Flag.FORCE_RETURN_VALUE) > ---------------------------------------------------------------------- > > Key: ISPN-5677 > URL: https://issues.jboss.org/browse/ISPN-5677 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.2.Final > Reporter: Shay Matasaro > Assignee: Galder Zamarreño > Fix For: 8.0.0.CR1, 8.0.0.Final > > > given the following HR client code > NotifyingFuture<String> f1 = cache.withFlags(Flag.FORCE_RETURN_VALUE).putIfAbsentAsync(key, "1"); > System.out.println(f1.get(10,TimeUnit.MINUTES)); > NotifyingFuture<String> f2 = cache.withFlags(Flag.FORCE_RETURN_VALUE).putIfAbsentAsync(key, "2"); > System.out.println(f2.get(10,TimeUnit.MINUTES)); > both prints print null, where the second one should print "1" > only when props.put("infinispan.client.hotrod.force_return_values","true") is set specifically when building the CM then the calls work -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5677) HR putIfAbsentAsync not enforcing withFlags(Flag.FORCE_RETURN_VALUE)

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5677?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5677: ----------------------------------- Fix Version/s: 8.0.0.CR1 8.0.0.Final > HR putIfAbsentAsync not enforcing withFlags(Flag.FORCE_RETURN_VALUE) > ---------------------------------------------------------------------- > > Key: ISPN-5677 > URL: https://issues.jboss.org/browse/ISPN-5677 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.2.Final > Reporter: Shay Matasaro > Assignee: Galder Zamarreño > Fix For: 8.0.0.CR1, 8.0.0.Final > > > given the following HR client code > NotifyingFuture<String> f1 = cache.withFlags(Flag.FORCE_RETURN_VALUE).putIfAbsentAsync(key, "1"); > System.out.println(f1.get(10,TimeUnit.MINUTES)); > NotifyingFuture<String> f2 = cache.withFlags(Flag.FORCE_RETURN_VALUE).putIfAbsentAsync(key, "2"); > System.out.println(f2.get(10,TimeUnit.MINUTES)); > both prints print null, where the second one should print "1" > only when props.put("infinispan.client.hotrod.force_return_values","true") is set specifically when building the CM then the calls work -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5517) JDBCBinaryStore size method should query count directly instead of iterating

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-5517?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-5517: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/3633, https://github.com/infinispan/infinispan/pull/3648 (was: https://github.com/infinispan/infinispan/pull/3633) > JDBCBinaryStore size method should query count directly instead of iterating > ---------------------------------------------------------------------------- > > Key: ISPN-5517 > URL: https://issues.jboss.org/browse/ISPN-5517 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: William Burns > Assignee: Ryan Emerson > Fix For: 8.0.0.Final > > > JDBCBinaryStore size method iterates upon all of the rows in the database. We should instead use the getCountRowsSql from the table manipulation just like JDBCStringBasedStore. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5664) Null is returned for a not expired entry in Hot Rod client

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5664?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-5664: ---------------------------------------- PR integrated, leaving it open till it's ported to 7.2.x. > Null is returned for a not expired entry in Hot Rod client > ---------------------------------------------------------- > > Key: ISPN-5664 > URL: https://issues.jboss.org/browse/ISPN-5664 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 8.0.0.Beta2 > Reporter: William Burns > Assignee: William Burns > Fix For: 8.0.0.CR1, 7.2.5.Final > > > For a mortal entry (lifespan > -1), overwriting it with lifespan=-1 (make it immortal) unexpectedly removes the entry like follows. > ~~~ > cache.put(key, "value1", 100, TimeUnit.SECONDS, 100, TimeUnit.SECONDS); > cache.get(key); // returns "value1" > cache.put(key, "value2", -1, TimeUnit.SECONDS, 100, TimeUnit.SECONDS); > cache.get(key); // returns null, expected "value2" > cache.put(key, "value3", -1, TimeUnit.SECONDS, 100, TimeUnit.SECONDS); > cache.get(key); // returns "value3" > ~~~ > In library mode, the 2nd get returns non-null as expected. The same behaviour is observed for a transient (maxIdle > -1) entry also. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5670) Hot Rod server sets -1 for lifespan or maxIdle as default

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5670?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-5670: ---------------------------------------- PR integrated, leaving it open till it's ported to 7.2.x. > Hot Rod server sets -1 for lifespan or maxIdle as default > --------------------------------------------------------- > > Key: ISPN-5670 > URL: https://issues.jboss.org/browse/ISPN-5670 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Reporter: William Burns > Assignee: William Burns > Fix For: 8.0.0.CR1, 7.2.5.Final > > > The hotrod server currently keeps the default lifespan and maxIdle in the CacheDecodeContext. This works fine however a metadata is generated ignoring that if -1 is passed. Instead the put(K, V, Metadata) merges the default metadata into the one generated, which won't have a lifespan or maxIdle set since it was -1. In this case the merge method will take the default value instead. We should explicitly set the metadata to -1 before calling put(K, V, Metadata) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 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 August 2015