[
https://issues.apache.org/jira/browse/IGNITE-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yakov Zhdanov updated IGNITE-1163:
----------------------------------
Fix Version/s: (was: sprint-8)
ignite-1.4
> getOrCreateNearCache should work when ignite configuration contains cache
> configuration
> ---------------------------------------------------------------------------------------
>
> Key: IGNITE-1163
> URL: https://issues.apache.org/jira/browse/IGNITE-1163
> Project: Ignite
> Issue Type: Task
> Reporter: Alexey Goncharuk
> Fix For: ignite-1.4
>
>
> * Create an Ignite configuration instance that contains cache configuration
> * Start a client node with this configuration
> * On client call {{getOrCreateNearCache}}
> Currently in this scenario near cache will not be created because internally
> an instance of client cache is created on node start. Later, when
> {{getOrCreateNearCache}} is called, exchange happens, but
> {{GridCacheProcessor#prepareCacheStart}} returns due to the check {{if
> (sharedCtx.cacheContext(CU.cacheId(cfg.getName())) != null)}}
> In this case Ignite should check that near cache is being started and current
> context is not near, so existing context should be destroyed, all existing
> cache proxies should be invalidated and new cache context and cache proxy
> should be created.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
