[infinispan-issues] [JBoss JIRA] Commented: (ISPN-905) Enhance cache management methods on EmbeddedCacheManager
[
https://issues.jboss.org/browse/ISPN-905?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño commented on ISPN-905:
---------------------------------------
I see the point for CacheManager.remove(String). There's two things that need some
thought: First, how to make CacheManager.remove() wait for on-going txs to finish, within
a time period of course (I think Cache.stop() should do as well. although as you said the
target is different - I'll open a diff jira for this). The second is how to deal with
concurrent CacheManager.remove() calls for the same cache, particularly coming from diff
nodes.
I don't understand the need for cacheExists()/getCacheIfExists() yet. What is the use
case for this from a client's perspective? In other words, what would you do if a
cache does not exist? What would you do different?
Enhance cache management methods on EmbeddedCacheManager
--------------------------------------------------------
Key: ISPN-905
URL: https://issues.jboss.org/browse/ISPN-905
Project: Infinispan
Issue Type: Feature Request
Components: Core API
Affects Versions: 4.2.0.Final
Reporter: Patrick McFarland
Assignee: Galder Zamarreño
Fix For: 5.0.0.ALPHA3, 5.0.0.Final
These should include:
{code:borderStyle=solid}
boolean cacheExists(String cache)
Cache<?, ?> getCacheIfExists(String cache)
boolean remove(String Cache)
{code}
Original request:
{quote}
There seems to be no ability to check if a populated cache exists through both
CacheManager and through Cache (=is this still a valid handle) and to get a cache if it
exists.
{quote}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira