Hi Juan, > the returned set is always null. As soon as an empty configuration is > passed, the set seems to work again. Is this the intended behavior? Yes, this is the intended behavior. Ignite#set() method returns a named set from cache and create one if it has not been created yet and CollectionConfiguration is not null [1].
>Should from 2.1.0 onwards caches/sets with different requirements be stored in different cache groups? Yes, distributed Sets/Queues within the same group must have the same cache mode, affinity function and so on. Thanks! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cache-Groups-and-PARTITIONED-REPLICATED-tp15853p15867.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
