[
https://issues.jboss.org/browse/ISPN-905?page=com.atlassian.jira.plugin.s...
]
Patrick McFarland commented on ISPN-905:
----------------------------------------
As far as I can tell, Cache.stop() would only delete the contents if it is local only, and
not written to disk; nor does running Cache.stop() on one cluster member effect other
cluster members, their Cache instances remain started.
Cache.remove() should stop the cache on all members of the cluster and also delete whats
on disk (if it is backed by a persistent disk store). Indeed, having a cache defined in
the config would not effect this either way.
(cacheExists()/getCacheIfExists()) should return (true/the cache) if has been started
(locally) and/or has data written to disk (cluster wide). If it is neither started locally
nor any cluster member has a disk store for it, then it should return (false/null).
I also agree that stop() should also be transaction safe; I already assumed it was from
the way IS is designed.
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