Hello! I think it makes sense.
I think we should not over-engineer it now. Let's just allow to specify your own CacheConfiguration and take all the risks. Regards, -- Ilya Kasnacheev вт, 2 июн. 2020 г. в 17:37, Vladimir Pligin <vova199...@yandex.ru>: > Hi Igniters! > > It seems that AtomicConfiguration > ( > https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/AtomicConfiguration.html > ) > is not flexible enough to cover some reasonable use-cases. It's possible to > configure only cache mode, group name, affinity and backups of the > underlying cache. It would be great to have the ability to inject > full-fledged CacheConfiguration there. For example there's no > straightforward way to configure a node filter, this scenario can be useful > as sometimes it's required to avoid atomic sequence residence on a subset > of > nodes. > > What do you think about it, are there any pitfalls? > > > > -- > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ >
