[
https://issues.apache.org/jira/browse/IGNITE-9233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588496#comment-16588496
]
Ivan Pavlukhin edited comment on IGNITE-9233 at 8/27/18 2:20 PM:
-----------------------------------------------------------------
MERGE behavior was broken in such way that it acts like UPDATE.
was (Author: pavlukhin):
MERGE behavior was broken it such way that it acts like UPDATE.
> MVCC SQL: False write conflicts on fast updates
> -----------------------------------------------
>
> Key: IGNITE-9233
> URL: https://issues.apache.org/jira/browse/IGNITE-9233
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
> Reporter: Ivan Pavlukhin
> Assignee: Ivan Pavlukhin
> Priority: Major
> Attachments: MvccInsertDeleteConcurrent.java
>
>
> Currently is possible to encounter query failure e.g. in case when DELETE
> with directly specified key encounters write conflict for row which is
> created by concurrent INSERT. From SNAPSHOT isolation point of view DELETE
> either should not see a row and do nothing or should remove a row gracefully.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
