[
https://issues.apache.org/jira/browse/CASSANDRA-14919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-14919:
----------------------------------------
Resolution: Fixed
Fix Version/s: (was: 3.11.x)
(was: 3.0.x)
3.11.4
3.0.18
Status: Resolved (was: Patch Available)
I'm all for helping our future selves and I hope that the comments and link to
this discussion will do that. I've stopped short of enforcing the expectations
though, as what we have now fixes the breakage introduced by 14568/14749/14912
whilst retaining the fixes from those issues. It also preserves the behaviour
of previous 3.0/3.x versions so I think this has the minimal risk of
introducing new, unforeseen regressions. If it does transpire that there other
cases where this existing behaviour is harmful, or this patch breaks something
else we didn't consider, we can revisit then.
Committed to 3.0 in {{11043610e38281f650f289a7f9286d306f1369e3}} and merged to
3.11/trunk, thanks.
> 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.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.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
