If you're executing a query from the same transaction where you updated the data, I'm pretty sure you can find a workaround, because you know everything about the updates made within the transaction. Transactional SQL feature is mostly designed to avoid dirty reads in case a query transaction and update transaction are two separate concurrent transactions.
-Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Query-does-not-include-objects-added-into-Cache-from-within-a-transaction-tp7651p7717.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
