[jira] [Updated] (IGNITE-3478) Transactional SQL

["Alexey Goncharuk (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Goncharuk updated IGNITE-3478:
-------------------------------------
    Assignee: Sergi Vladykin

> Transactional SQL
> -----------------
>
>                 Key: IGNITE-3478
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3478
>             Project: Ignite
>          Issue Type: Task
>          Components: cache
>            Reporter: Alexey Goncharuk
>            Assignee: Sergi Vladykin
>             Fix For: 2.0
>
>
> 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.3.4#6332)