Cos, How you are going to create caches in already started cluster? I think you will create a cache configuration and after that will get cache via Ignite.getOrCreateCache(ccfg).
So if you server cluster at some point was completely restarted, then executing getOrCreateCache(ccfg) will create cache again (if needed) or return existing cache. Also AFAIK CacheConfiguration class is serializable - you can save it somewhere and later load if needed. Or you may define some XML files with cache beans and load them with IgniteSpringHelper. Thoughts? On Tue, Dec 22, 2015 at 3:32 PM, Konstantin Boudnik <[email protected]> wrote: > Guys, > > is it possible to configure caches dynamically and persist their > configuration > in some shape and form? Here's the use case: > - we want to create some caches in the already running cluster for a data > set > - once it is done, we'll run some SQL queries on top of those > - ideally, we'd like to be able to safe the cache configurations so next > time, we don't need to do the structures and field types discovery, but > instead be able to load it on (re)start > > Is this a supported use-case or everything should be defined statically > before > nodes start? Looks like the latter, but perhaps we are missing something. > > Thanks in advance for any info, > Cos > -- Alexey Kuznetsov GridGain Systems www.gridgain.com
