[CASSANDRA-9699] Make choice of sstable reader types explicit

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0 alpha 1
• Assignee: Benedict Elliott Smith
• Reporter: Benedict Elliott Smith

Authors

Benedict Elliott Smith

Reviewers

Marcus Eriksson

• Created: 01/Jul/15 15:49
• Updated: 16/Apr/19 09:31
• Resolved: 28/Jul/15 09:29

Description

CASSANDRA-9580 made it apparent that the efforts to isolate unsafe users of early opened results wasn't quite fully successful.

This patch attempts to impose some minor central refactors that force the (internal) user to specify if they want the live sstable set, or the "canonical" sstable set (or just the "noncompacting" set, since this is the intersection of the two). It also eliminates a lot of ugliness and some duplication around filtration, and obsoletes the CANONICAL_SSTABLES and UNREPAIRED_SSTABLES functions in ColumnFamilyStore, which were very ugly.

Issue Links

• is related to: CASSANDRA-6916 Preemptive opening of compaction result