While we are contemplating the best way to introduce this feature I have a side note to consider. Can the user enable CacheStore (RDBMS, Cassandra) for caches that are not persisted in Ignite Persistence? That’s one of the use cases I hear a lot about - some of the caches need persisted in Ignite Persistence while the rest in a 3rd party storage.
Think it makes sense to support this use case as a part of this work. — Denis > On Sep 12, 2017, at 2:24 AM, Alexey Goncharuk <alexey.goncha...@gmail.com> > wrote: > > Igniters, > > I am currently reviewing a change allowing to enable persistence on a > per-memory-policy basis (thanks to K. Dudkov!) and have a question > regarding the changes in configuration. > > The suggested change is to add a flag "persistenceEnabled" (defaults to > true) to the memory policy configuration. To keep configuration > compatibility, the logic is as follows: > > If PersistentStoreConfiguration is set, then only memory policies with > persistenceEnabled=true flag will be persisted, which is consistent with > the current behavior. To disable persistence, persistenceEnabled flag > should be explicitly set to false. > > If PersistentStoreConfiguration is not set, then all caches are stored > in-memory and persistenceEnabled is ignored. > > While personally, I like this change, I would like to check if there are > any thoughts or objections to this approach. > > -- > Thanks, > AG
