ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-3478) Transactional SQL
Date Fri, 03 Feb 2017 12:13:51 GMT

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

Vladimir Ozerov updated IGNITE-3478:
------------------------------------
    Fix Version/s:     (was: 2.0)

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

Mime
View raw message