Yukang-Lian opened a new pull request, #67600:
URL: https://github.com/apache/doris/pull/67600
### What problem does this PR solve?
Issue Number: None
Related PR: #64954, #65470
Problem Summary: Backport the cumulative-compaction large-head fix from
#64954 to `branch-3.1`, together with the final mergeable-input protection from
#65470.
#64954 removes the promotion-size early return so level-size trimming can
exclude an oversized leading rowset instead of repeatedly compacting it. It
also keeps the last suffix rowset available for the singleton checks. The same
behavior is applied to the cloud and local size-based policies.
`branch-3.1` predates the deferred max-score tail-trimming mechanism changed
by #65470, so that later implementation cannot be cherry-picked directly. This
backport preserves #65470's final invariant in the branch's collection-time
guard: trimming must not strand a single non-overlapping rowset when its direct
successor is needed to form a mergeable input. Focused cloud and local
regression cases cover both the stranded-head and overlapping-singleton
max-score scenarios.
The source commits are `a1e076e8d6969feafd8411f7b19e22664f43c543` (#64954)
and `54300f922fddbeac6e679a83d7829444d4a72f77` (#65470). The branch is based on
the latest `branch-3.1` at publication time.
### Release note
Avoid repeatedly compacting an oversized cumulative rowset while keeping
trimmed inputs mergeable on branch-3.1.
### Check List (For Author)
- Test: Regression coverage added for both cloud and local
cumulative-compaction policies
- Clang Format 16 changed-line check: passed
- `git diff --check`: passed
- Full branch-specific BE unit tests were not run locally; hosted CI is
requested below
- Behavior changed: Yes
- Allows level-size trimming to exclude an oversized leading rowset
- Preserves a mergeable successor for singleton inputs
- Does this need documentation: No
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
