[
https://issues.apache.org/jira/browse/CASSANDRA-14919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
C. Scott Andreas updated CASSANDRA-14919:
-----------------------------------------
Complexity: Challenging
Discovered By: Unit Test
Bug Category: Parent values: Availability(12983)Level 1 values:
Unavailable(12994)
Since Version: 3.0.0
> Regression in paging queries in mixed version clusters
> -------------------------------------------------------
>
> Key: CASSANDRA-14919
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14919
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter, Messaging/Internode, Messaging/Thrift
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Urgent
> Fix For: 3.0.18, 3.11.4
>
>
> The changes to handling legacy bounds in
> CASSANDRA-14568/CASSANDRA-14749/CASSANDRA-14912 break paging queries where
> the coordinator is a legacy node and the replica is an upgraded node.
> The long-held assumption made by {{LegacyLayout::decodeBound}} that "There
> can be more components than the clustering size only in the case this is the
> bound of a collection range tombstone." is not true as serialized paged read
> commands may also include these type of bounds in their {{SliceQueryFilter}}.
> The additional checks the more recent tickets add cause such queries to error
> when processed by a 3.0 replica.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
