[
https://issues.apache.org/jira/browse/IGNITE-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-3479:
-------------------------------------
Fix Version/s: (was: 2.0)
2.1
> Global transaction ordering
> ---------------------------
>
> Key: IGNITE-3479
> URL: https://issues.apache.org/jira/browse/IGNITE-3479
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
> Reporter: Alexey Goncharuk
> Fix For: 2.1
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
