You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Yury Gerzhedovich (JIRA)" <ji...@apache.org> on 2018/08/24 14:22:00 UTC

[jira] [Commented] (IGNITE-6044) SQL insert waits for transaction commit, but it must be executed right away

    [ https://issues.apache.org/jira/browse/IGNITE-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16591733#comment-16591733 ] 

Yury Gerzhedovich commented on IGNITE-6044:
-------------------------------------------

[Test results|https://ci.ignite.apache.org/viewLog.html?buildId=1725151&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_ContinuousQuery2]

> SQL insert waits for transaction commit, but it must be executed right away
> ---------------------------------------------------------------------------
>
>                 Key: IGNITE-6044
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6044
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>    Affects Versions: 2.1
>            Reporter: Mikhail Cherkasov
>            Assignee: Yury Gerzhedovich
>            Priority: Critical
>              Labels: sql-stability, usability
>
> Doc says:
> ""Presently, DML supports the atomic mode only meaning that if there is a DML query that is executed as a part of an Ignite transaction then it will not be enlisted in the transaction's writing queue and will be executed right away.""
> https://apacheignite.readme.io/docs/dml#section-transactional-support
> However the data will be added to cache only after transaction commit.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)