Val, The logic you describe changed a while ago, with introduction of persistent storage and cache group mechanics. Currently there might exist multiple special caches where data structures are stored. The main reason for it was to give users ability to put different structures into different cache groups, and configure which ones should be persistent and which shouldn't.
On Wed, Apr 11, 2018 at 2:33 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Guys, > > I also not sure I understand the purpose of methods like [1] that accept > instance of AtomicConfiguration to create new atomic structure. Per my > knowledge, all atomics are stored in a single cache which is configured by > AtomicConfiguration provided on startup as part of IgniteConfiguration. If > that's the case, providing another configuration for a particular atomic > doesn't make sense because it will never be used. > > Any thoughts on this? Unless I'm missing something, I think we can > deprecate these methods. > > [1] > https://ignite.apache.org/releases/latest/javadoc/org/ > apache/ignite/Ignite.html#atomicLong-java.lang.String-org.apache.ignite. > configuration.AtomicConfiguration-long-boolean- > > -Val > > On Tue, Apr 10, 2018 at 3:28 PM, Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: > > > On Tue, Apr 10, 2018 at 2:03 PM, akurbanov <antkr....@gmail.com> wrote: > > > > > Dmitry, > > > > > > Sorry for confusing topic. I I'm pretty sure that configuration for > > atomic > > > caches is validated, will double-check this. I was referring only > atomic > > > data structures cache. > > > > > > > Got it. We should definitely add validation for the atomic data > structures > > configuration as well. > > > -- Best regards, Ilya
