[
https://issues.apache.org/jira/browse/CASSANDRA-20092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17928024#comment-17928024
]
Branimir Lambov commented on CASSANDRA-20092:
---------------------------------------------
The test results I committed with are
[here|https://app.circleci.com/pipelines/github/blambov/cassandra/850/workflows/92552a0b-7483-46b9-ba0f-c05ff6469267]
and had no junit failures.
This is a 5.1 patch – we may want it in 5.0 as well as 4.0, but I haven't made
patches for those versions.
> 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: 0.5h
> 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: [email protected]
For additional commands, e-mail: [email protected]
