You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Ariel Weisberg (Jira)" <ji...@apache.org> on 2024/02/26 19:34:00 UTC

[jira] [Commented] (CASSANDRA-19431) Mutations need to split Accord/non-Accord mutations based on whether migration is completed

    [ https://issues.apache.org/jira/browse/CASSANDRA-19431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17820827#comment-17820827 ] 

Ariel Weisberg commented on CASSANDRA-19431:
--------------------------------------------

This one is narrowly scoped to just splitting and routing the mutations which can be done today without the others, but still won't be correct until it can also detect mutations sent to the wrong place and then retry them without generating an error.

> Mutations need to split Accord/non-Accord mutations based on whether migration is completed
> -------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-19431
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19431
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Ariel Weisberg
>            Priority: Normal
>
> If we don't do this then requests will fail if they span Accord and non-Accord keys and tables. This breaks unlogged batches for example.



--
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