[
https://issues.apache.org/jira/browse/CASSANDRA-20788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-20788:
--------------------------------------
Bug Category: Parent values: Correctness(12982)Level 1 values:
Unrecoverable Corruption / Loss(13161)
Complexity: Low Hanging Fruit
Discovered By: Fuzz Test
Fix Version/s: 6.x
Severity: Critical
Status: Open (was: Triage Needed)
> 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
>
>
> {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: [email protected]
For additional commands, e-mail: [email protected]
