ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Goncharuk <alexey.goncha...@gmail.com>
Subject Re: Persistence per memory policy configuration
Date Tue, 12 Sep 2017 14:54:35 GMT

The default=true will be used only if the PersistentStoreConfiguration is
set in the IgniteConfiguration, this is done only to maintain configuration

A user is allowed to use persisted and in-memory caches, he will be only
forced to put them into separate memory policies.

2017-09-12 13:39 GMT+03:00 Yakov Zhdanov <yzhdanov@apache.org>:

> Agree that implicit actions are always source of issues of different kinds.
> Alex, having persistence enabled by default does not seem to be a good
> idea.
> >I think if we go with "persistence per cache" path, we must just enforce
> the
> correct configuration and let users configure the rest
> What do you mean by enforce? What if user mixes persisted and in-mem
> caches?
> --Yakov

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message