Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Duplicate
-
None
-
None
-
Normal
Description
We currently only notify compaction strategies about when we get a new instance of an sstable reader - for example when we move the start position. We don't notify when we create a new 'temporary' sstable when opening early.
We should probably only track actual files, with their original first/last keys to make it easier for compaction strategies to not have to keep track of what files are 'real' and what files have had their starts moved etc.
Attachments
Issue Links
- duplicates
-
CASSANDRA-8568 Extend Transactional API to sstable lifecycle management
- Resolved
- is related to
-
CASSANDRA-6916 Preemptive opening of compaction result
- Resolved