I also not sure I understand the purpose of methods like  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.
On Tue, Apr 10, 2018 at 3:28 PM, Dmitriy Setrakyan <dsetrak...@apache.org>
> 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
> > 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.