Description
Current transaction ID will not work for SQL MVCC ordering because two transaction IDs are not in total order across the cluster.
One of the approaches is to have a dedicated coordinator which will assign a continuously growing transaction ID for each committed transaction. This ID must be acquired by each transaction at the last step of PREPARE stage.
Attachments
Issue Links
- Is contained by
-
IGNITE-6874 MVCC: base functionality
- Closed