[ https://issues.apache.org/jira/browse/CASSANDRA-14823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648595#comment-16648595 ]
Blake Eggleston commented on CASSANDRA-14823: --------------------------------------------- [~benedict] [~iamaleksey] would one (or both) of you mind taking a look at this as well? > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org