Skip to content

[test](paimon) Verify Paimon null partition refresh and rewrite - #70201

Merged
suxiaogang223 merged 1 commit into
apache:masterfrom
suxiaogang223:codex/paimon-null-partition-mtmv-regression
Nov 5, 2026
Merged

suxiaogang223 merged 1 commit into
apache:masterfrom
suxiaogang223:codex/paimon-null-partition-mtmv-regression

Conversation

@suxiaogang223

Copy link
Copy Markdown
Member

What problem does this PR solve?

Related PRs: #65904, #64304

The existing Paimon MTMV regression covers the initial refresh of a NULL partition. This test covers an out-of-band Spark append to that partition after the initial refresh. It verifies that the stale partition is ineligible for rewrite, automatic refresh touches only the NULL partition, and the refreshed MV is chosen again. The string partition 'null' is a control.

The suite compares live SQL results and checks the rewrite plan without a golden output file. This PR adds regression coverage only.

Release note

None

Check List (For Author)

  • Test: git diff --check passed. Doris compilation and regression execution were not run.
  • Behavior changed: No
  • Does this need documentation: No

### What problem does this PR solve?

Issue Number: N/A

Related PR: N/A

Problem Summary: Cover an external append to an existing Paimon NULL partition after the initial asynchronous materialized view refresh. Verify the stale partition is excluded from query rewrite, automatic refresh replaces only that partition, and the refreshed view is used again.

### Release note

None

### Check List (For Author)

- Test: Static diff check passed. Regression execution is pending review.
- Behavior changed: No
- Does this need documentation: No
@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?

@suxiaogang223

Copy link
Copy Markdown
Member Author

run buildall

@suxiaogang223
suxiaogang223 merged commit b69168c into apache:master Nov 5, 2026
38 checks passed
@suxiaogang223
suxiaogang223 deleted the codex/paimon-null-partition-mtmv-regression branch November 5, 2026 08:52
@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

PR approved by anyone and no changes requested.

@github-actions github-actions Bot added the approved Indicates a PR has been approved by one committer. label Nov 5, 2026
@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

PR approved by at least one committer and no changes requested.

github-actions Bot pushed a commit that referenced this pull request Nov 5, 2026
### What problem does this PR solve?

Related PRs: #65904, #64304

The existing Paimon MTMV regression covers the initial refresh of a NULL
partition. This test covers an out-of-band Spark append to that
partition after the initial refresh. It verifies that the stale
partition is ineligible for rewrite, automatic refresh touches only the
NULL partition, and the refreshed MV is chosen again. The string
partition 'null' is a control.

The suite compares live SQL results and checks the rewrite plan without
a golden output file. This PR adds regression coverage only.

### Release note

None

### Check List (For Author)

- Test: `git diff --check` passed. Doris compilation and regression
execution were not run.
- Behavior changed: No
- Does this need documentation: No
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by one committer. dev/4.1.x dev/4.2.x reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants