You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Yakov Zhdanov (JIRA)" <ji...@apache.org> on 2015/06/23 16:35:08 UTC
[jira] [Updated] (IGNITE-929) IgniteCache.close should not delete
the cache from the cluster
[ https://issues.apache.org/jira/browse/IGNITE-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yakov Zhdanov updated IGNITE-929:
---------------------------------
Fix Version/s: (was: sprint-6)
sprint-7
> IgniteCache.close should not delete the cache from the cluster
> --------------------------------------------------------------
>
> Key: IGNITE-929
> URL: https://issues.apache.org/jira/browse/IGNITE-929
> Project: Ignite
> Issue Type: Bug
> Reporter: Alexey Goncharuk
> Assignee: Anton Vinogradov
> Fix For: sprint-7
>
>
> Need to introduce IgniteCache.destroy() method instead. close() method should be implemented differently for LOCAL and distributed caches
> * For LOCAL cache close() should be equivalent to destroyCache()
> * For distributed caches close(), if called on clients, should close client cache, but not destroy cache on the whole cluster.
> * For distributed caches close(), if called on a server node, should be a no-op
> TCK should run with LOCAL cache.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)