I still think that continuous queries fit you use case much better. It will update you once for each update and make all this filtering automatically. Moreover, after https://issues.apache.org/jira/browse/IGNITE-426 is finished, it will provide consistent updates even on changing topology (will notify from backup in case primary node crashes).
With events you can use Affinity.isPrimary(node, key) method to check if local node is primary for the updated key, but this will work properly only on stable topology. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cache-Events-Questions-tp1090p1243.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
