Skip to content

branch-4.0: [test](schema-change) log alter job state in test_schema_change_mow_with_empty_rowset#65230

Open
shuke987 wants to merge 1 commit into
apache:branch-4.0from
shuke987:fix-4.0-schema-change-mow-empty-rowset-log
Open

branch-4.0: [test](schema-change) log alter job state in test_schema_change_mow_with_empty_rowset#65230
shuke987 wants to merge 1 commit into
apache:branch-4.0from
shuke987:fix-4.0-schema-change-mow-empty-rowset-log

Conversation

@shuke987

@shuke987 shuke987 commented Jul 6, 2026

Copy link
Copy Markdown
Collaborator

Summary

Cherry-pick #64903 to branch-4.0.

This adds the polled schema-change job state to
test_schema_change_mow_with_empty_rowset logs so future branch-4.0 failures
show whether the job is still running or has become CANCELLED.

This is a logging-only backport and does not change the case assertion or the
Cloud MOW schema-change behavior. The product-side delete-bitmap lock failure
for this case is still tracked separately by DORIS-26740.

Testing

  • Cherry-picked cleanly onto branch-4.0
  • Verified diff is one inserted logger.info line
  • Not run locally; requires a Doris Cloud branch-4.0 regression environment

…ith_empty_rowset (apache#64903)

## Proposed changes

Add a `logger.info` to print the alter table job state that is polled
inside the Awaitility loop in
`test_schema_change_mow_with_empty_rowset.groovy`.

The test waits for the schema-change job to reach `FINISHED`/`CANCELLED`
but does not log the intermediate state. When the job stalls or ends up
`CANCELLED`, the regression log shows no trace of the observed state,
making failures hard to diagnose. Logging the polled `res` each
iteration makes such failures self-explanatory from the test output.

No behavior change to the test logic itself.

## Checklist
- [x] No new test needed (logging-only change to an existing regression
test)
🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
(cherry picked from commit 3860c27)
@shuke987 shuke987 requested a review from morningman as a code owner July 6, 2026 03:31
@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

shuke987 commented Jul 6, 2026

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