Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
None
-
Normal
Description
Now that we use SinglePartitionNamesCommand in more places - where we'd previously use what is now SinglePartitionSliceCommand - not being able to skip sstables with non-overlapping clusterings is actually a performance regression.
SinglePartitionNamesCommand::queryMemtableAndDiskInternal should prune sstables based on ClusteringIndexNamesFilter::shouldInclude output, and the latter must be replaced with an actual implementation instead of a TODO.
This is also a potentially a big regression in performance for counter writes (say, with DTCS), since before 3.0, the read-before-write code would use collectAllData, and that was pruning sstable with non-overlapping clusterings.