I've added a code example to github
I appreciate any help here as it basically means there's no way to guarantee
read-after-write consistency for events triggered off of a transaction
involving multiple caches, even if they access the data in exactly the same
order as the transaction changed it.
View this message in context:
Sent from the Apache Ignite Users mailing list archive at Nabble.com.