Skip to content

branch-4.0: [fix](regression) Disable auto compaction in manual compaction cases #65211#65532

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

branch-4.0: [fix](regression) Disable auto compaction in manual compaction cases #65211#65532
github-actions[bot] wants to merge 1 commit into
branch-4.0from
auto-pick-65211-branch-4.0

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Cherry-picked from #65211

…65211)

## Proposed changes

- Disable table-level auto compaction in regression cases that
explicitly call `trigger_and_wait_compaction(...)`.
- Cover manual compaction checks in compaction, schema_change, cloud
cache/balance, point_query, and variant analyzer cases.
- Keep shared DDL changes local to the case call sites where possible.

## Why

These cases want to control compaction timing through explicit helper
calls. If table auto compaction is still enabled, background compaction
can consume the target rowsets first, making the manual trigger get
ignored or observe a different intermediate rowset state.

## Validation

- `git diff --cached --check`
- `git diff --check`
- Scanned `regression-test/suites` for
`trigger_and_wait_compaction(...)`; remaining files without inline table
property are external-DDL cases already disabling auto compaction, or
internal statistics tables without case-owned DDL.
@github-actions github-actions Bot requested a review from morningman as a code owner July 13, 2026 08:39
@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