In this case you should mark the implementation with @CacheLocalStore annotation, which will force Ignite to pass entry version along with the value during write-through. You can then use it to maintain consistency. But this is a pretty challenging task and implementing local store is way more complicated than implementing the shared store. So I would rethink the approach and see if this can be done in a different way.
-Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/CacheStore-with-replication-tp9087p9100.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
