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 15:00:00 UTC
[jira] [Commented] (CASSANDRA-14919) Regression in paging queries
in mixed version clusters
[ https://issues.apache.org/jira/browse/CASSANDRA-14919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708819#comment-16708819 ]
Sam Tunnicliffe commented on CASSANDRA-14919:
---------------------------------------------
This issue showed up during work on CASSANDRA-14421 to re-enable the upgrade dtests. Using [~aweisberg]'s dtest branch as a starting point, I've verified that the upgrade tests concerned with paging are now passing (after some additional tweaks - see CASSANDRA-14920). I've only run this locally though and haven't updated the CircleCI config to add those tests, leaving that to 14421.
The CircleCI runs below are running with the current dtest master branch:
||branch||CI||
|[14919-3.0|https://github.com/beobal/cassandra/tree/14919-3.0]|[circle|https://circleci.com/gh/beobal/workflows/cassandra/tree/cci%2F14919-3.0]|
|[14919-3.11|https://github.com/beobal/cassandra/tree/14919-3.11]|[circle|https://circleci.com/gh/beobal/workflows/cassandra/tree/cci%2F14919-3.11]|
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org