ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vkulichenko <valentin.kuliche...@gmail.com>
Subject Re: Is CacheConfiguration specified at client node ignored in case if Cache already exists?
Date Sun, 10 Jan 2016 05:10:48 GMT

Ignite.createCache() method will throw an exception if the cache already
exists. But if you use Ignite.getOrCreateCache() method instead, it will be
either created with the provided configuration, or you will get an already
existing cache. In the latter case the configuration you provide will be
ignored. There is also Ignite.cache() method that you can use when you're
sure cache already exists. It accepts just a cache name instead of
CacheConfiguration object.

Makes sense?


View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Is-CacheConfiguration-specified-at-client-node-ignored-in-case-if-Cache-already-exists-tp2461p2476.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message