Skip to content

branch-4.1: [fix](compaction) Use row count for cumulative task classification #66706 - #66938

Open
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-66706-branch-4.1
Open

branch-4.1: [fix](compaction) Use row count for cumulative task classification #66706#66938
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-66706-branch-4.1

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #66706

…66706)

Problem Summary:

`CompactionMixin::calc_input_rowsets_row_num()` calculated input rowset
disk size instead of row count. As a result, cumulative compaction task
classification compared bytes with
`large_cumu_compaction_task_row_num_threshold`, which could incorrectly
treat compactions with small row count but disk size over the threshold
value as large tasks.

This PR fixes the calculation to sum `rowset->num_rows()` and adds a BE
unit test to verify row-count calculation is independent from total-size
calculation.

### Release note

None

### Check List (For Author)

- Test
  - [ ] Regression test
  - [✅] Unit Test
  - [ ] Manual test
  - [ ] No need to test or manual test.


- Behavior changed:
  - [✅] No.
  - [ ] Yes.

- Does this need documentation?
  - [✅] No.
  - [ ] Yes.
@github-actions
github-actions Bot requested a review from yiguolei as a code owner August 19, 2026 07:24
@hello-stephen

Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@hello-stephen

Copy link
Copy Markdown
Contributor

run buildall

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants