June 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3216) NullPointerException when preload with AsyncStore in Transactional caches

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3216?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3216: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > NullPointerException when preload with AsyncStore in Transactional caches > ------------------------------------------------------------------------- > > Key: ISPN-3216 > URL: https://issues.jboss.org/browse/ISPN-3216 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 5.2.6.Final, 5.3.0.CR1 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 5.2.7.Final, 5.3.0.CR2 > > > AsyncStore tries to commit a transaction from preload, however this transaction has the modification list to null causing the NPE when tries to query the size. > It only happens in the transactional caches. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2657) Support for LevelDB CacheStore

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2657?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2657: -------------------------------- Fix Version/s: 5.2.7.Final > Support for LevelDB CacheStore > ------------------------------ > > Key: ISPN-2657 > URL: https://issues.jboss.org/browse/ISPN-2657 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Reporter: Ray Tsang > Assignee: Manik Surtani > Fix For: 5.2.7.Final, 5.3.0.Final > > > Support for LevelDB, a fast key-value persistence storage. > There is a pure java implementation and a jni by fuse -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2657) Support for LevelDB CacheStore

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2657?page=com.atlassian.jira.plugin.... ] Mircea Markus resolved ISPN-2657. --------------------------------- Assignee: Ray Tsang (was: Manik Surtani) Resolution: Done Integrated - thanks Ray! > Support for LevelDB CacheStore > ------------------------------ > > Key: ISPN-2657 > URL: https://issues.jboss.org/browse/ISPN-2657 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Reporter: Ray Tsang > Assignee: Ray Tsang > Fix For: 5.2.7.Final, 5.3.0.Final > > > Support for LevelDB, a fast key-value persistence storage. > There is a pure java implementation and a jni by fuse -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1540) Refactor distribution interceptor

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-1540?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-1540: ------------------------------------- Also need to make sure that read from remote are put into the L1 cache right away instead of putting it in the tx context. This comment talks about that. https://issues.jboss.org/browse/ISPN-2965?focusedCommentId=12779780&page=... > Refactor distribution interceptor > --------------------------------- > > Key: ISPN-1540 > URL: https://issues.jboss.org/browse/ISPN-1540 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Affects Versions: 5.1.0.BETA5 > Reporter: Mircea Markus > Assignee: William Burns > Fix For: 6.0.0.Final > > > DistributionInterceptor, as it looks now is unnecessary complex. Before adding more functionality on top of it (i.e. ISPN-1539) it should be refactored: > - extract L1 logic into a different interceptor > - this would require moving the StateTransferLock logic into another interceptor as well > - now that we have separation between tx and non-tx caches, we can extract the remaining logic into TransactionalDistributionInterceptor and NonTransactional... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1540) Refactor distribution interceptor

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-1540?page=com.atlassian.jira.plugin.... ] William Burns reassigned ISPN-1540: ----------------------------------- Assignee: William Burns (was: Mircea Markus) > Refactor distribution interceptor > --------------------------------- > > Key: ISPN-1540 > URL: https://issues.jboss.org/browse/ISPN-1540 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Affects Versions: 5.1.0.BETA5 > Reporter: Mircea Markus > Assignee: William Burns > Fix For: 6.0.0.Final > > > DistributionInterceptor, as it looks now is unnecessary complex. Before adding more functionality on top of it (i.e. ISPN-1539) it should be refactored: > - extract L1 logic into a different interceptor > - this would require moving the StateTransferLock logic into another interceptor as well > - now that we have separation between tx and non-tx caches, we can extract the remaining logic into TransactionalDistributionInterceptor and NonTransactional... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3200) Allow KeyFilters to be applied to listeners

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3200?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3200: -------------------------------- Labels: leads (was: ) > Allow KeyFilters to be applied to listeners > ------------------------------------------- > > Key: ISPN-3200 > URL: https://issues.jboss.org/browse/ISPN-3200 > Project: Infinispan > Issue Type: Feature Request > Components: Listeners > Affects Versions: 5.3.0.Final > Reporter: Manik Surtani > Assignee: Mircea Markus > Labels: leads > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > > When registering a listener, users should be able to provide a {{KeyFilter}}, a simple interface that determines whether a listener is invoked or not based on whether the affected key(s) matches the filter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3201) Allow listeners to be invoked only by a primary data owner

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3201?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3201: -------------------------------- Labels: leads (was: ) > Allow listeners to be invoked only by a primary data owner > ---------------------------------------------------------- > > Key: ISPN-3201 > URL: https://issues.jboss.org/browse/ISPN-3201 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache, Listeners > Affects Versions: 5.3.0.Final > Reporter: Manik Surtani > Assignee: Mircea Markus > Labels: leads > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > > Could be a parameter on the annotation, such as {{primaryOwnerOnly}} to prevent all replicas from firing updates. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-132) Distributed queue/list API

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-132?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-132: ------------------------------- Labels: leads (was: ) > Distributed queue/list API > -------------------------- > > Key: ISPN-132 > URL: https://issues.jboss.org/browse/ISPN-132 > Project: Infinispan > Issue Type: Feature Request > Components: Core API, Fine-grained API > Reporter: Bryan Grunow > Assignee: Manik Surtani > Labels: leads > Fix For: 7.0.0.Final > > > Original request: > {quote} > Add support for retrieving entries from the cache (simple API and Tree API) via insertion (FIFO) order. > For example, cache.getNext(); would return the next entry in the queue. > {quote} > Updating this JIRA to provide an API for a collection that can be appended to without retrieving the entire collection. Essentially a list, with various concurrent access guarantees. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3198) Allow multiple versions of entries to be stored

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3198?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3198: -------------------------------- Labels: leads versioning (was: versioning) > Allow multiple versions of entries to be stored > ----------------------------------------------- > > Key: ISPN-3198 > URL: https://issues.jboss.org/browse/ISPN-3198 > Project: Infinispan > Issue Type: Feature Request > Components: Core API > Affects Versions: 5.3.0.Final > Reporter: Manik Surtani > Assignee: Mircea Markus > Labels: leads, versioning > Fix For: 7.0.0.Final > > > Storing multiple versions of a given entry will pave the way for eventual consistency based on vector clocks as well as the ability for API-controlled versioning. > Will require that each entry is a structure that contains multiple actual entries ordered by version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3199) API to manipulate multiple versions of an entry

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3199?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3199: -------------------------------- Labels: leads (was: ) > API to manipulate multiple versions of an entry > ----------------------------------------------- > > Key: ISPN-3199 > URL: https://issues.jboss.org/browse/ISPN-3199 > Project: Infinispan > Issue Type: Feature Request > Components: Core API > Affects Versions: 5.3.0.Final > Reporter: Manik Surtani > Assignee: Mircea Markus > Labels: leads > Fix For: 7.0.0.Final > > > In addition to the existing API, the following will be needed to allow user applications to directly control versioning. E.g., > {code} > put(K key, EntryVersion version); > get(K key, EntryVersion version); > getLatest(K key, EntryVersion upperBound); > evict(K key, EntryVersion upTo); > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2013