[
https://issues.apache.org/jira/browse/CASSANDRA-20092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17899710#comment-17899710
]
Benedict Elliott Smith commented on CASSANDRA-20092:
----------------------------------------------------
You are probably correct, I haven't recently refreshed my memory or familiarity
with the nest of different classes and behaviours. I assume the scrubber
originally used this class (and assumed it still did, which clearly it does
not). Either way, I only wanted to note it for consideration.
> SSTableScanner can be vastly simplified for compaction
> ------------------------------------------------------
>
> Key: CASSANDRA-20092
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20092
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Compaction
> Reporter: Branimir Lambov
> Priority: Normal
>
> One of the main bottlenecks for compaction performance is its use of the
> {{SSTableScanner}} class, whose main purpose is to implement partition range
> queries and as such supports filtering by row and column that is not helpful
> to compaction. To implement the latter it must rely on the sstable's index,
> adding a lot of complexity and inefficiency.
> Implementing a simpler version of a scanner that reads off the data file
> directly for given spans of offsets would speed up compaction significantly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
