[ https://issues.apache.org/jira/browse/CASSANDRA-14919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708969#comment-16708969 ]
Sam Tunnicliffe commented on CASSANDRA-14919: --------------------------------------------- {quote}Typo in the links to the code{quote} oops, actually a failure to push those 2 branches. Fixed now > 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 > Priority: Critical > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org