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 2024/03/29 17:13:00 UTC

[jira] [Assigned] (CASSANDRA-19503) (Accord) Cassandra bootstrap no longer using the range txn and instead uses the sync point empty txn for reads

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

David Capwell reassigned CASSANDRA-19503:
-----------------------------------------

    Assignee: David Capwell

> (Accord) Cassandra bootstrap no longer using the range txn and instead uses the sync point empty txn for reads
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-19503
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19503
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Accord
>            Reporter: David Capwell
>            Assignee: David Capwell
>            Priority: Normal
>
> Ephemeral reads made a change to ReadData which caused Bootstrap to no longer use the range txn it generates and instead uses the empty txn from the sync point.  This was not detected in Accord due to ListRead supporting ranges, and failed in Cassandra as we don’t support range reads.



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