[
https://issues.apache.org/jira/browse/CASSANDRA-20092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17945889#comment-17945889
]
Jordan West commented on CASSANDRA-20092:
-----------------------------------------
This has been backported to 5.0 in
https://github.com/apache/cassandra/commit/f327b63db09a907206749a3c88aba38a4554e548
Additionally I have backported the fix in CASSANDRA-20396 in
https://github.com/apache/cassandra/commit/17cb89208c804680ffd4445d6a826171a67edb79
> SSTableScanner can be vastly simplified for compaction
> ------------------------------------------------------
>
> Key: CASSANDRA-20092
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20092
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Local/Compaction
> Reporter: Branimir Lambov
> Assignee: Branimir Lambov
> Priority: Normal
> Fix For: 5.1
>
> Attachments: ci_summary_thelastpickle_mck-20092-5.0_154.html,
> results_details_thelastpickle_mck-20092-5.0_154.tar.xz
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
