[
https://issues.apache.org/jira/browse/IGNITE-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610518#comment-16610518
]
Taras Ledkov commented on IGNITE-6044:
--------------------------------------
[~jooger], the review status:
| Codestyle | Please review my minor changes |
| Documentation | Please link documentation issue |
| Binary compatibility | - |
| Tests | Please run all SQL suites |
| Comments | # I guess {{DmlInsideTransactionTest.SystemProperty}} must keep
the original property value because property may be setup externally for suite
etc.
# {{SystemProperty}} looks usable. Does make sense move it to
{{org.apache.ignite.testframework}} or {{GridTestUtils}}?|
> 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)
