Yes, I just realized that you don't have write-through, so delete operations are not propagated to the DB. In this case the behavior you're describing looks correct from Ignite standpoint. If you update something directly in the DB, but Ignite then loads old values from the DB, most likely the bug is in your cache store implementation. Did you try to debug it?
-Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Removing-or-overwriting-cache-value-but-still-able-to-get-it-from-the-cache-tp6334p6396.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
