February 2014 - infinispan-issues

[JBoss JIRA] (ISPN-4036) StateConsumerImpl.isKeyUpdated searches for the key in the values collection

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4036?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4036: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2401 > StateConsumerImpl.isKeyUpdated searches for the key in the values collection > ---------------------------------------------------------------------------- > > Key: ISPN-4036 > URL: https://issues.jboss.org/browse/ISPN-4036 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 7.0.0.Alpha1 > > > Introduced by the ISPN-3443 fix. I changed the {{updatedKeys}} HashSet to be an EquivalendConcurrentHashMap, but I forgot to change the {{contains(key)}} call to {{containsKey(key)}}. Since we use the same value for all the keys, it means state transfer might skip more keys than it should have. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4054) Scripts to analyze test failures and corresponding issues

by Dan Berindei (JIRA)

Dan Berindei created ISPN-4054: ---------------------------------- Summary: Scripts to analyze test failures and corresponding issues Key: ISPN-4054 URL: https://issues.jboss.org/browse/ISPN-4054 Project: Infinispan Issue Type: Task Components: Test Suite - Core Affects Versions: 6.0.1.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 7.0.0.Alpha1 Need an easy way to find scripts that fail in CI but don't have a corresponding issue in JIRA, or are not in the unstable group. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4002) Allow the reduce phase to store elements into an intermediate cache

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4002?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-4002: ------------------------------------ [~mircea.markus] [~vblagojevic] I suppose this is about specifying a results cache, not an intermediary cache? > Allow the reduce phase to store elements into an intermediate cache > -------------------------------------------------------------------- > > Key: ISPN-4002 > URL: https://issues.jboss.org/browse/ISPN-4002 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Distributed Execution and Map/Reduce > Reporter: Mircea Markus > Assignee: Vladimir Blagojevic > > In the situation in which the result of the Map/Reduce task is large, returning it to the originator does not work, as the originator would run OOM. In order to drop this limitation, would be good to: > - have a result cache > - put all the M/R entries into this result cache > It should be possible to specify this cache to the Map/Reduce task to be executed (cache name), as users might reuse the cache and configure it externally. > > The caller will be notified once the data Map/Reduce is finished. We'd need a way for the user to get all the keys in this cache for further processing. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4021) Allow each Map/Reduce task to use a different cache configuration

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4021?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-4021: ------------------------------------ Actually, the application code would never need to work with the intermediate cache directly, or care about the types in the intermediate cache, so I think option b) should be enough. > Allow each Map/Reduce task to use a different cache configuration > ----------------------------------------------------------------- > > Key: ISPN-4021 > URL: https://issues.jboss.org/browse/ISPN-4021 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Distributed Execution and Map/Reduce > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: Vladimir Blagojevic > Fix For: 7.0.0.Final > > > Some Map/Reduce tasks may need a cache store and eviction, some may not. Each task should be able to use its own cache configuration. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4021) Allow each Map/Reduce task to use a different cache configuration

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4021?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-4021: ------------------------------------ [~vblagojevic], can't we support both? > Allow each Map/Reduce task to use a different cache configuration > ----------------------------------------------------------------- > > Key: ISPN-4021 > URL: https://issues.jboss.org/browse/ISPN-4021 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Distributed Execution and Map/Reduce > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: Vladimir Blagojevic > Fix For: 7.0.0.Final > > > Some Map/Reduce tasks may need a cache store and eviction, some may not. Each task should be able to use its own cache configuration. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2686) Enhance Mapper API with lazy loaded value

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-2686?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-2686: ------------------------------------------- This requires API changes - use of a new mapper interface. I'd say lets leave it and see if more people request something like this. I would rather not complicate things further unless it is really necessary. > Enhance Mapper API with lazy loaded value > ----------------------------------------- > > Key: ISPN-2686 > URL: https://issues.jboss.org/browse/ISPN-2686 > Project: Infinispan > Issue Type: Enhancement > Components: Distributed Execution and Map/Reduce > Affects Versions: 5.2.0.Beta6 > Reporter: Thomas Fromm > Assignee: Vladimir Blagojevic > Priority: Minor > > In situations where Map/Reduce is used and the value is not (always) needed at the Mapper, the value could be loaded lazy, when the map(..) interface is slightly changed: > map(Entry<KIn, VIn> entry, Collector<Entry<KIn, VIn>> collector) > When entry.getValue() is called, the value should be loaded from store or maybe remote node. > Maybe this change to Entry would be also useful for event api ISPN-1802 -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4021) Allow each Map/Reduce task to use a different cache configuration

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-4021?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-4021: ------------------------------------------- [~mircea.markus] What do you think about this? > Allow each Map/Reduce task to use a different cache configuration > ----------------------------------------------------------------- > > Key: ISPN-4021 > URL: https://issues.jboss.org/browse/ISPN-4021 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Distributed Execution and Map/Reduce > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: Vladimir Blagojevic > Fix For: 7.0.0.Final > > > Some Map/Reduce tasks may need a cache store and eviction, some may not. Each task should be able to use its own cache configuration. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4018) Write skew should not be check if conditional operations does not change the value

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4018?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4018: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Write skew should not be check if conditional operations does not change the value > ---------------------------------------------------------------------------------- > > Key: ISPN-4018 > URL: https://issues.jboss.org/browse/ISPN-4018 > Project: Infinispan > Issue Type: Bug > Components: Core, Transactions > Affects Versions: 6.0.1.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > Currently, if a conditional operation does no perform the update, we still perform the check. however, the write never happened. It simple makes no sense. > However, if a write succeeds after, the write skew check must be performed for the key. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3899) XAResourceRecovery implementation needed for transaction recovery in library mode

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3899?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-3899: ------------------------------------- [~jmarkos] I think the XAResource that you need to register with TM's XAResourceRecoveryRegistry is the one that can be obtained through: cache.getAdvancedCache().getXAResource(). Paul, any idea why that wouldn't work? > XAResourceRecovery implementation needed for transaction recovery in library mode > --------------------------------------------------------------------------------- > > Key: ISPN-3899 > URL: https://issues.jboss.org/browse/ISPN-3899 > Project: Infinispan > Issue Type: Bug > Components: Transactions > Reporter: Galder Zamarreño > Assignee: Ion Savin > Fix For: 7.0.0.Final > > > According to [~pferraro], an implementation of XAResourceRecovery needs to be added to Infinispan and plugged into XAResourceRecoveryRegistry in order to get recovery of XA transactions working as expected. > This is already done in Server/AS/Wildfly in org.jboss.as.clustering.infinispan.subsystem.CacheService class. > A similar thing should happen when Infinispan is used in embedded/library mode. > [~isavin], since you are going to work on the transaction changes in 7.0, maybe you can take this on too? It'd be interesting to add a test to start with which shows that XA transaction recovery is not working as expected as a result of not having this. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4047) Use the sort criteria provided by hql-parser (after fixing HQLPARSER-24)

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4047?page=com.atlassian.jira.plugin.... ] Work on ISPN-4047 started by Adrian Nistor. > Use the sort criteria provided by hql-parser (after fixing HQLPARSER-24) > ------------------------------------------------------------------------ > > Key: ISPN-4047 > URL: https://issues.jboss.org/browse/ISPN-4047 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Remote Querying > Affects Versions: 6.0.1.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > Currently we have separate handling of the sort criteria in Infinispan because the JPQL parser skips it. See https://hibernate.atlassian.net/browse/HQLPARSER-24. -- 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

10 years, 11 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 2014