[
https://issues.apache.org/jira/browse/CASSANDRA-20788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18010723#comment-18010723
]
David Capwell commented on CASSANDRA-20788:
-------------------------------------------
Starting commit
CI Results (pending):
||Branch||Source||Circle CI||Jenkins||
|trunk|[branch|https://github.com/dcapwell/cassandra/tree/commit_remote_branch/CASSANDRA-20788-trunk-CC8AF895-948F-4D15-AAB5-0AD24600091E]|[build|unknown]|[build|unknown]|
> When using BEGIN TRANSACTION if a complex mutation exists in the same
> statement as one that uses a reference, then the complex delete is dropped
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-20788
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20788
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Accord
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: 6.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
> BEGIN TRANSACTION
> LET row = (SELECT *
> FROM distributed_test_keyspace.accordtbl0
> WHERE k = ? AND c = ?);
> UPDATE distributed_test_keyspace.accordtbl0
> SET
> v0={1},
> v1 += row.v1
> WHERE
> k = ? AND
> c = ?;
> COMMIT TRANSACTION
> {code}
> You would expect that v0={1} after this runs, but assuming it was {0} before
> hand the output is {0, 1}. The reason is that the complex delete gets lost
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
