Skip to content

[fix](case) test_p_seq_publish_read_from_old: disable auto compaction to stabilize qt_inspect#64508

Open
shuke987 wants to merge 1 commit into
apache:branch-4.1from
shuke987:fix-test-p-seq-publish-disable-compaction
Open

[fix](case) test_p_seq_publish_read_from_old: disable auto compaction to stabilize qt_inspect#64508
shuke987 wants to merge 1 commit into
apache:branch-4.1from
shuke987:fix-test-p-seq-publish-disable-compaction

Conversation

@shuke987

Copy link
Copy Markdown
Collaborator

Problem

test_p_seq_publish_read_from_old is flaky on the branch-4.1 P0 regression. The qt_inspect queries read physical rows (skip_delete_sign / skip_delete_bitmap); background auto compaction merges rowsets and changes the physical row count, so the inspected output drifts from the .out. The final logical data is correct — only the inspected physical rows fluctuate with compaction timing.

Fix

Add "disable_auto_compaction" = "true" to the table PROPERTIES, matching the sibling cases in the same directory, so the inspection is stable.

Verification

Ran the suite on a branch-4.1 local cluster (3 FE + 4 BE) — passes.

🤖 Generated with Claude Code

… to stabilize qt_inspect

The qt_inspect queries read physical rows (skip_delete_sign / skip_delete_bitmap).
Background auto compaction merges rowsets and changes the physical row count, so the
inspected output drifts from the .out file, making the case flaky on branch-4.1 P0.
The final logical data is correct; only the inspected physical rows fluctuate with
compaction timing. Disable auto compaction so the inspection is stable, matching the
sibling cases in the same directory.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@shuke987 shuke987 requested a review from yiguolei as a code owner June 15, 2026 06:52
@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?

@shuke987

Copy link
Copy Markdown
Collaborator Author

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