You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Igor Seliverstov (JIRA)" <ji...@apache.org> on 2018/04/06 11:44: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 ]

Igor Seliverstov updated IGNITE-3478:
-------------------------------------
    Fix Version/s:     (was: 2.5)
                   2.6

> 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
>            Priority: Major
>              Labels: important
>             Fix For: 2.6
>
>
> 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
(v7.6.3#76005)