You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/11/13 07:12:00 UTC
[jira] [Updated] (IGNITE-3478) Multi-version concurrency control
[ https://issues.apache.org/jira/browse/IGNITE-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-3478:
------------------------------------
Summary: Multi-version concurrency control (was: Transactional SQL (mvcc))
> Multi-version concurrency control
> ---------------------------------
>
> Key: IGNITE-3478
> URL: https://issues.apache.org/jira/browse/IGNITE-3478
> Project: Ignite
> Issue Type: New Feature
> Components: cache
> Reporter: Alexey Goncharuk
> Assignee: Semen Boikov
> Labels: important
>
> Current Ignite SQL does not take into account transaction boundaries. For example, if a transaction atomically changes balance of two accounts, then a concurrent SQL query can see partially committed transaction. This works for data analytics, but does not work for more strict and demanding scenarios.
> It would be perfect if we had a mode which ensures transaction boundaries are taken into account for SQL query.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)