You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Pligin (Jira)" <ji...@apache.org> on 2020/06/04 10:02:00 UTC

[jira] [Created] (IGNITE-13118) Make AtomicConfiguration more customizable

Vladimir Pligin created IGNITE-13118:
----------------------------------------

             Summary: Make AtomicConfiguration more customizable
                 Key: IGNITE-13118
                 URL: https://issues.apache.org/jira/browse/IGNITE-13118
             Project: Ignite
          Issue Type: Improvement
          Components: data structures
    Affects Versions: 2.8.1
            Reporter: Vladimir Pligin
            Assignee: Vladimir Pligin


*Description of the issue:*

_AtomicConfiguration_ ([https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/AtomicConfiguration.html]) is not flexible enough to cover some reasonable scenarios at the moment. It's possible to configure cache mode, group name, affinity and backups of the underlying cache only. For example there's no straightforward way to configure a node filter. It can be handful as sometimes it's required to avoid atomic sequence residence on a subset of nodes.

*Proposed solution:*

Make injection of a full-fledged _CacheConfiguration_ possible during a construction process of _AtomicConfiguration_. . 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)