Sam, It sounds like you can set CacheConfiguration#invalidate property to true. This will force Ignite to invalidate near cache entry on update rather that syncing it with a new value. Is this what you're looking for?
-Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Event-Listeners-tp8306p14503.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
