July 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-1833) Add EmbeddedCacheManager.getGlobalComponentRegistry

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1833?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1833: -------------------------------- Priority: Minor (was: Major) > Add EmbeddedCacheManager.getGlobalComponentRegistry > --------------------------------------------------- > > Key: ISPN-1833 > URL: https://issues.jboss.org/browse/ISPN-1833 > Project: Infinispan > Issue Type: Enhancement > Components: Core API > Reporter: Galder Zamarreño > Assignee: Manik Surtani > Priority: Minor > Fix For: 6.0.0.Final > > > You should be able to retrieve the global component registry out of the EmbeddedCacheManager. > Rather that having to do: > cache.getAdvancedCache().getComponentRegistry().getGlobalComponentRegistry() -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-374) Add event handling to Hot Rod

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-374?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-374: ------------------------------- Fix Version/s: (was: 6.0.0.Final) > Add event handling to Hot Rod > ----------------------------- > > Key: ISPN-374 > URL: https://issues.jboss.org/browse/ISPN-374 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: hackathon > > Enable Hot Rod servers to send events asynchronously to registered clients over persistent connections. This would allow use cases such as clients maintaining L1 caches and these events could be used for servers to invalidate keys on the client side. See dev list thread for more info. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1957) Improve internal data structures in the L1Manager

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1957?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1957: -------------------------------- Priority: Minor (was: Major) > Improve internal data structures in the L1Manager > ------------------------------------------------- > > Key: ISPN-1957 > URL: https://issues.jboss.org/browse/ISPN-1957 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Affects Versions: 5.1.3.FINAL > Reporter: Manik Surtani > Assignee: Manik Surtani > Priority: Minor > Labels: data_structures > Fix For: 6.0.0.Final > > > The L1Manager contains a multimap of keys to servers and their timestamps, to know where to send invalidation messages. This is currently implemented as a CHM of CHMs, and can be very bulky and inefficient. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1957) Improve internal data structures in the L1Manager

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1957?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1957: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Improve internal data structures in the L1Manager > ------------------------------------------------- > > Key: ISPN-1957 > URL: https://issues.jboss.org/browse/ISPN-1957 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Affects Versions: 5.1.3.FINAL > Reporter: Manik Surtani > Assignee: Manik Surtani > Priority: Minor > Labels: data_structures > > The L1Manager contains a multimap of keys to servers and their timestamps, to know where to send invalidation messages. This is currently implemented as a CHM of CHMs, and can be very bulky and inefficient. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1905) Ability to specify lifespan for AtomicMaps through AtomicMapLookup API

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1905?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1905: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Ability to specify lifespan for AtomicMaps through AtomicMapLookup API > ---------------------------------------------------------------------- > > Key: ISPN-1905 > URL: https://issues.jboss.org/browse/ISPN-1905 > Project: Infinispan > Issue Type: Feature Request > Components: Core API > Affects Versions: 5.1.2.FINAL > Reporter: Guido Bonazza > Assignee: Manik Surtani > > Currently there is no way to specify the lifespan of an AtomicMap when it is created through AtomicMapLookup. > Some overloads of AtomicMapLookup#getAtomicMap() and AtomicMapLookup#getFineGrainedAtomicMap() should be provided that take the (..., long lifespan, TimeUnit unit) extra parameters. > See the forum reference for a workaround. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3280) HotRod client should depend on commons and not core

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3280?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3280: ---------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan/pull/1939, https://github.com/infinispan/infinispan/pull/1941 (was: https://github.com/infinispan/infinispan/pull/1939) > HotRod client should depend on commons and not core > --------------------------------------------------- > > Key: ISPN-3280 > URL: https://issues.jboss.org/browse/ISPN-3280 > Project: Infinispan > Issue Type: Sub-task > Components: Remote protocols > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1090) Hot Rod protocol improvements for version 2

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1090?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1090: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Hot Rod protocol improvements for version 2 > ------------------------------------------- > > Key: ISPN-1090 > URL: https://issues.jboss.org/browse/ISPN-1090 > Project: Infinispan > Issue Type: Enhancement > Components: Remote protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > > This JIRA will act as a place to keep track of enhancements to the Hot Rod protocol that should be included in version 2 of the protocol: > - We need a new error status code so that clients can detect when a node has been suspected and so react accordingly (i.e. not bubble it up but instead failover). Currently, this can be solved by checking whether the error message contains SuspectException but this is not nice. > - Since we're not gonna be supporting asymmetric clusters in the mean time, we need a new error status code to deal with situations where the cache is not defined in the server. Currently we check for CacheNotFoundException in the message but that's not nice. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-984) Add ability to retrieve cache names remotely in Hot Rod

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-984?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-984: ------------------------------- Fix Version/s: (was: 6.0.0.Final) > Add ability to retrieve cache names remotely in Hot Rod > ------------------------------------------------------- > > Key: ISPN-984 > URL: https://issues.jboss.org/browse/ISPN-984 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: hotrod > > A new operation would be needed to retrieve all cache names that are configured and running. > A new version of the protocol would need to be set up to deal with the new operation. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2143) Improve how different indexed caches sync up on new indexed types

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2143?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2143: -------------------------------- Fix Version/s: 6.0.0.Final (was: 6.0.0.Alpha1) > Improve how different indexed caches sync up on new indexed types > ----------------------------------------------------------------- > > Key: ISPN-2143 > URL: https://issues.jboss.org/browse/ISPN-2143 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Labels: stable_embedded_query > Fix For: 6.0.0.Final > > > Currently when a node receives an unknown type, it doesn't inform all other nodes, which might fail to get metadata and index boot information from it. > Also, the list of known types should be stored somewhere. > When a shared index is used, we might be able to load some type names from the index itself, but unfortunately usually we need the type name to initialize the index. Rely on an index storage convention? > See also comments in {{org.infinispan.query.indexmanager.IndexUpdateCommand}} -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2143) Improve how different indexed caches sync up on new indexed types

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2143?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2143: -------------------------------- Assignee: Adrian Nistor (was: Sanne Grinovero) > Improve how different indexed caches sync up on new indexed types > ----------------------------------------------------------------- > > Key: ISPN-2143 > URL: https://issues.jboss.org/browse/ISPN-2143 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Reporter: Sanne Grinovero > Assignee: Adrian Nistor > Labels: stable_embedded_query > Fix For: 6.0.0.Final > > > Currently when a node receives an unknown type, it doesn't inform all other nodes, which might fail to get metadata and index boot information from it. > Also, the list of known types should be stored somewhere. > When a shared index is used, we might be able to load some type names from the index itself, but unfortunately usually we need the type name to initialize the index. Rely on an index storage convention? > See also comments in {{org.infinispan.query.indexmanager.IndexUpdateCommand}} -- 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

12 years, 9 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 July 2013