[CASSANDRA-14838] Dropped columns can cause reverse sstable iteration to return prematurely

• Type: Bug
• Status: Resolved
• Priority: Urgent
• Resolution: Fixed
• Fix Version/s: 3.0.18, 3.11.4, 4.0-alpha1, 4.0
• Component/s: Local/SSTable
• Bug Category: Correctness - Transient Incorrect Response
• Severity: Critical
• Complexity: Challenging
• Discovered By: Fuzz Test
• Since Version: 3.0.0
• Assignee: Blake Eggleston
• Reporter: Blake Eggleston

Authors

Blake Eggleston

Reviewers

Sam Tunnicliffe

• Created: 23/Oct/18 19:45
• Updated: 15/May/20 08:03
• Resolved: 29/Oct/18 02:45

Description

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