Hello,
In short, Apache Ignite's SQL engine executes DML statements on top of
committed data without creating a snapshot. So, in order to provide fully
transactional SQL, SQL engine should be built on top of new MVCC protocol.
Please take a look at the following Ignite enhancement proposal (IEP):
hi vkulichenko
I may not express myself clearly，What I mean is that since KV storage
supports transactions, why doesn't SQL support transactional transactions?
Dose Transaction impact other session‘s select SQL？
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
This is being developed now, here is the ticket you can track:
https://issues.apache.org/jira/browse/IGNITE-4191
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
hi
I know that Ignite support transactional mode transaction as KV store, then
why SQL not support?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
