[infinispan-issues] [JBoss JIRA] Commented: (ISPN-905) Enhance cache management methods on EmbeddedCacheManager

[Patrick McFarland (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579255#comment-12579255 ] 

Patrick McFarland commented on ISPN-905:
----------------------------------------

remove() should also be transaction safe, as in if I have transactions open that will write to a cache, and I've told the cluster to delete the cache, the transactions should not fail, and the cache should not be reopened (as in, all written data is also deleted/never stored after the transaction completes).

The end state should end up being all transactions completed, all future attempted transactions involving that cache (assuming I use getCacheIfExists habitually) will fail, and all use of existing Cache handles created before the delete fail, and no node should have any information on the deleted cache.

tl;dr: it shouldn't leak

> 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: Manik Surtani
>             Fix For: 5.0.0.BETA1, 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