You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sam Tunnicliffe (JIRA)" <ji...@apache.org> on 2018/12/04 10:25:00 UTC
[jira] [Created] (CASSANDRA-14919) Regression in paging queries in
mixed version clusters
Sam Tunnicliffe created CASSANDRA-14919:
-------------------------------------------
Summary: 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
Reporter: Sam Tunnicliffe
Assignee: Sam Tunnicliffe
Fix For: 3.0.x, 3.11.x
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.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org