Re: Continuous query not transactional ?

2020-10-16 Thread VeenaMithare
Hi Ilya, That is what I assume too, could someone from the developers community help confirm/comment on this ? regards, Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Continuous query not transactional ?

2020-10-16 Thread Ilya Kasnacheev
Hello! I'm not sure, but I would assume that changes are visible after commit(), but you can see these changes in any order, and you can see cache a update without cache b update, for example. This is for committed transactions. For rolled back transactions, I don't know. I expect you won't be

Continuous query not transactional ?

2020-10-15 Thread VeenaMithare
Hi , This is in continuation of the below statement on this post : http://apache-ignite-users.70518.x6.nabble.com/Lag-before-records-are-visible-after-transaction-commit-tp33787p33861.html >>Continuous Query itself is not transactional and it looks like it can't be used for this at the moment.