Skip to content

Conversation

@zddr
Copy link
Contributor

@zddr zddr commented Dec 11, 2024

What problem does this PR solve?

Previously, when refreshing the materialized view according to the partition name, the existing partition of the materialized view was used to verify whether the partition name existed
After the change, the partition that should be present after refreshing the materialized view is used for verification

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:
Change the way to verify the existence of partition names when refreshing MTMV

Release note

Change the way to verify the existence of partition names when refreshing MTMV

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason
  • Behavior changed:

    • No.
    • Yes.
  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

@doris-robot
Copy link

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?

@zddr
Copy link
Contributor Author

zddr commented Dec 11, 2024

run buildall

@zddr
Copy link
Contributor Author

zddr commented Dec 11, 2024

run p0

@morrySnow morrySnow added dev/2.1.x dev/3.0.x usercase Important user case type label labels Dec 13, 2024
@zddr
Copy link
Contributor Author

zddr commented Dec 13, 2024

run buildall

@zddr
Copy link
Contributor Author

zddr commented Dec 13, 2024

run p0

@github-actions
Copy link
Contributor

PR approved by anyone and no changes requested.

@github-actions
Copy link
Contributor

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

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Dec 16, 2024
@morrySnow morrySnow merged commit fc512ab into apache:master Dec 20, 2024
27 of 28 checks passed
github-actions bot pushed a commit that referenced this pull request Dec 20, 2024
…mes when refreshing MTMV (#45290)

### What problem does this PR solve?

Previously, when refreshing the materialized view according to the
partition name, the existing partition of the materialized view was used
to verify whether the partition name existed
After the change, the partition that should be present after refreshing
the materialized view is used for verification
github-actions bot pushed a commit that referenced this pull request Dec 20, 2024
…mes when refreshing MTMV (#45290)

### What problem does this PR solve?

Previously, when refreshing the materialized view according to the
partition name, the existing partition of the materialized view was used
to verify whether the partition name existed
After the change, the partition that should be present after refreshing
the materialized view is used for verification
yiguolei pushed a commit that referenced this pull request Dec 23, 2024
…partition names when refreshing MTMV #45290 (#45725)

Cherry-picked from #45290

Co-authored-by: zhangdong <zhangdong@selectdb.com>
yiguolei pushed a commit that referenced this pull request Dec 23, 2024
…partition names when refreshing MTMV #45290 (#45723)

Cherry-picked from #45290

Co-authored-by: zhangdong <zhangdong@selectdb.com>
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/2.1.8-merged dev/3.0.4-merged reviewed usercase Important user case type label

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants