Motivation

At the moment Apache Ignite's SQL engine doesn't support transactions. SELECT statements are executed on top of committed data without creating a snapshot. DML statements are executed as a series of batched updates using IgniteCache.invokeAll command. As a result it is neither possible to get consistent view of data, nor to update it with ACID semantics.

We need to implement transactions support in SQL on top new MVCC protocol.

Description

Locks

TBD

Isolation modes

TBD

Transactional SELECT

TBD

Transactional DML

TBD

Native API changes

TBD

Drivers support (JDBC/ODBC)

TBD

Cross-cache transactions

TBD

Risks and Assumptions

TBD

Discussion Links

N/A

Reference Links

N/A

Tickets