August 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5714) Add value/metadata aware store expiration listener

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5714?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5714: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/3683 > Add value/metadata aware store expiration listener > -------------------------------------------------- > > Key: ISPN-5714 > URL: https://issues.jboss.org/browse/ISPN-5714 > Project: Infinispan > Issue Type: Sub-task > Components: Expiration > Reporter: William Burns > Assignee: William Burns > Fix For: 8.0.0.Final > > > Expiration listener for stores currently only provide the key in a calback. It would be preferred if a store is able to also tell us the value and/or metadata so we can properly expire this entry across the cluster. The current implementation can expire incorrect values due to the fact that -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5653) keySet().iterator() does not propagate flags to remove()

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5653?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5653: ----------------------------------------------- Matej Čimbora <mcimbora(a)redhat.com> changed the Status of [bug 1254178|https://bugzilla.redhat.com/show_bug.cgi?id=1254178] from ON_QA to VERIFIED > keySet().iterator() does not propagate flags to remove() > -------------------------------------------------------- > > Key: ISPN-5653 > URL: https://issues.jboss.org/browse/ISPN-5653 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.2.3.Final, 8.0.0.Beta2 > Reporter: Radim Vansa > Assignee: William Burns > Fix For: 8.0.0.Beta3, 7.2.4.Final, 8.0.0.Final > > > Calling {{remove()}} on iterator obtained through keySet() does not propagate flags from the original (decorated) cache. Test case (should go into BaseEntryRetrieverTest): > {code} > @Test > public void simpleTestWithFlags() { > Map<Object, String> values = putValuesInCache(); > final Cache<Object, Object> cache = cache(0, CACHE_NAME); > cache.getAdvancedCache().addInterceptor(new BaseCustomInterceptor() { > @Override > public Object visitRemoveCommand(InvocationContext ctx, RemoveCommand command) throws Throwable { > assertTrue(command.hasFlag(Flag.SKIP_CACHE_STORE)); > return super.visitRemoveCommand(ctx, command); > } > }, 0); > for (Iterator it = cache(0, CACHE_NAME).getAdvancedCache().withFlags(Flag.SKIP_CACHE_STORE).keySet().iterator(); it.hasNext();) { > assertTrue(values.containsKey(it.next())); > it.remove(); > } > } > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5700) Create client expiration event

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5700?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5700: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated in master. Thanks [~william.burns]! > Create client expiration event > ------------------------------ > > Key: ISPN-5700 > URL: https://issues.jboss.org/browse/ISPN-5700 > Project: Infinispan > Issue Type: Sub-task > Components: Server > Reporter: William Burns > Assignee: William Burns > Fix For: 8.0.0.Final > > > We need client based expiration event as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5664?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5664: ----------------------------------------------- Matej Čimbora <mcimbora(a)redhat.com> changed the Status of [bug 1253052|https://bugzilla.redhat.com/show_bug.cgi?id=1253052] from ON_QA to VERIFIED > 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)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5714) Add value/metadata aware store expiration listener

by William Burns (JIRA)

William Burns created ISPN-5714: ----------------------------------- Summary: Add value/metadata aware store expiration listener Key: ISPN-5714 URL: https://issues.jboss.org/browse/ISPN-5714 Project: Infinispan Issue Type: Sub-task Components: Expiration Reporter: William Burns Assignee: William Burns Fix For: 8.0.0.Final Expiration listener for stores currently only provide the key in a calback. It would be preferred if a store is able to also tell us the value and/or metadata so we can properly expire this entry across the cluster. The current implementation can expire incorrect values due to the fact that -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5714) Add value/metadata aware store expiration listener

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5714?page=com.atlassian.jira.plugin.... ] Work on ISPN-5714 started by William Burns. ------------------------------------------- > Add value/metadata aware store expiration listener > -------------------------------------------------- > > Key: ISPN-5714 > URL: https://issues.jboss.org/browse/ISPN-5714 > Project: Infinispan > Issue Type: Sub-task > Components: Expiration > Reporter: William Burns > Assignee: William Burns > Fix For: 8.0.0.Final > > > Expiration listener for stores currently only provide the key in a calback. It would be preferred if a store is able to also tell us the value and/or metadata so we can properly expire this entry across the cluster. The current implementation can expire incorrect values due to the fact that -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5714) Add value/metadata aware store expiration listener

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5714?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5714: -------------------------------- Status: Open (was: New) > Add value/metadata aware store expiration listener > -------------------------------------------------- > > Key: ISPN-5714 > URL: https://issues.jboss.org/browse/ISPN-5714 > Project: Infinispan > Issue Type: Sub-task > Components: Expiration > Reporter: William Burns > Assignee: William Burns > Fix For: 8.0.0.Final > > > Expiration listener for stores currently only provide the key in a calback. It would be preferred if a store is able to also tell us the value and/or metadata so we can properly expire this entry across the cluster. The current implementation can expire incorrect values due to the fact that -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5713) Extend Continuous Query test coverage

by Vojtech Juranek (JIRA)

Vojtech Juranek created ISPN-5713: ------------------------------------- Summary: Extend Continuous Query test coverage Key: ISPN-5713 URL: https://issues.jboss.org/browse/ISPN-5713 Project: Infinispan Issue Type: Task Components: Test Suite - Query Reporter: Vojtech Juranek Assignee: Vojtech Juranek Implement test which * verifies that notification is sent also for expired entries * updates work correctly also for more complex queries which combines several predicates * updates work correctly when node a started/shut down -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5679) Add clustered expiration support

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5679?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5679: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add clustered expiration support > -------------------------------- > > Key: ISPN-5679 > URL: https://issues.jboss.org/browse/ISPN-5679 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: William Burns > Assignee: William Burns > Fix For: 8.0.0.Final > > > ISPN-694 added support for in memory expiration which is synchronized with the cache store. However we also need across clustered expiration synchronization. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

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

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5517?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5517: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/3633, https://github.com/infinispan/infinispan/pull/3648, https://github.com/infinispan/infinispan/pull/3680 (was: https://github.com/infinispan/infinispan/pull/3633, https://github.com/infinispan/infinispan/pull/3648) > 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.CR1, 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)

8 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2015