[
https://issues.apache.org/jira/browse/CASSANDRA-14838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
C. Scott Andreas updated CASSANDRA-14838:
-----------------------------------------
Severity: Critical (was: Normal)
Complexity: Challenging
Discovered By: Fuzz Test
Bug Category: Parent values: Correctness(12982)Level 1 values: Response
Corruption / Loss(12987)
Since Version: 3.0.0
Component/s: (was: Legacy/Local Write-Read Paths)
Local/SSTable
> Dropped columns can cause reverse sstable iteration to return prematurely
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-14838
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14838
> Project: Cassandra
> Issue Type: Bug
> Components: Local/SSTable
> Reporter: Blake Eggleston
> Assignee: Blake Eggleston
> Priority: Urgent
> Fix For: 3.0.18, 3.11.4, 4.0
>
>
> CASSANDRA-14803 fixed an issue where reading legacy sstables in reverse could
> return early in certain cases. It's also possible to get into this state with
> current version sstables if there are 2 or more indexed blocks in a row that
> only contain data for a dropped column. Post 14803, this will throw an
> exception instead of returning an incomplete response, but it should just
> continue reading like it does for legacy sstables
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
