[
https://issues.apache.org/jira/browse/CASSANDRA-14823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16650833#comment-16650833
]
Blake Eggleston commented on CASSANDRA-14823:
---------------------------------------------
Changes look good to me. Pulled in, merged to 3.11 and started another run of
tests:
|[3.0|https://github.com/bdeggleston/cassandra/tree/14823-3.0]|[circle|https://circleci.com/workflow-run/fd588958-4771-4d4e-8569-772415523c88]|
|[3.11|https://github.com/bdeggleston/cassandra/tree/14823-3.11]|[circle|https://circleci.com/workflow-run/37a12a6a-f2ab-4591-a5c7-83b926ba655a]|
> Legacy sstables with range tombstones spanning multiple index blocks create
> invalid bound sequences on 3.0+
> -----------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-14823
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14823
> Project: Cassandra
> Issue Type: Bug
> Reporter: Blake Eggleston
> Assignee: Blake Eggleston
> Priority: Major
> Fix For: 3.0.x, 3.11.x
>
>
> During upgrade from 2.1 to 3.0, reading old sstables in reverse order would
> generate invalid sequences of range tombstone bounds if their range
> tombstones spanned multiple column index blocks. The read fails in different
> ways depending on whether the 2.1 tables were produced by a flush or a
> compaction.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
