Manish, You can't change the filter at runtime, it's defined on cache startup. But the filter itself can be dynamic. For example, you can have a special attribute that defines whether the cache should be deployed or not (see IgniteConfiguration.setUserAttributes configuration property). When a new node joins, the cache will be deployed on this node if it has this attribute set.
Hope this helps. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Control-cache-datanodes-in-an-ignite-cluster-tp3216p3233.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
