You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "David Capwell (Jira)" <ji...@apache.org> on 2025/08/18 17:28:00 UTC

[jira] [Updated] (CASSANDRA-20844) BEGIN TRANSACTION crashes if a mutation touches multiple rows

     [ https://issues.apache.org/jira/browse/CASSANDRA-20844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Capwell updated CASSANDRA-20844:
--------------------------------------
     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)

> BEGIN TRANSACTION crashes if a mutation touches multiple rows
> -------------------------------------------------------------
>
>                 Key: CASSANDRA-20844
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20844
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: Accord
>            Reporter: David Capwell
>            Assignee: David Capwell
>            Priority: Normal
>             Fix For: 6.x
>
>
> This is forked from CASSANDRA-20828 to isolate the serialization changes.
> CQL operations such as the following cause BEGIN TRANSACTION to fail as this logic assumed mutations map to a single partition/row
> {code}
> UPDATE tbl … WHERE pk = 0 AND ck IN (0, 1, 2, 3);
> {code}
> This is allowed logic in normal CQL and is just fails due to a bad assumption when creating the write Fragments.  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org