-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](mtmv) before changing the mtmv status at the end of mtmv refres… #54144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…h, check if the base table status is SCHEMA_CHANGE
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Author
|
run buildall |
TPC-H: Total hot run time: 33901 ms |
TPC-DS: Total hot run time: 171705 ms |
ClickBench: Total hot run time: 33.27 s |
Contributor
FE UT Coverage ReportIncrement line coverage |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
When triggering a refresh mtmv task during schema change job, modify directly the mtmv status at the end of refresh mtmv, which resulted directly in the behavior of the materialized view being inconsistent with #49041
add check base table status before modifying the mtmv status at the end of the refresh mtmv task
Issue Number: close #xxx
Related PR: #49041
Problem Summary:
before changing the mtmv status at the end of mtmv refresh, check if the base table status is SCHEMA_CHANGE
Release note
None
Check List (For Author)
Test
Behavior changed:
During the execution of the scheme change task, queries which related to the base table ,cannot be rewritten with related asynchronous materialized views.
The previous logic was that after the refresh task was completed, the materialized view could be rewritten.
Does this need documentation?
Check List (For Reviewer who merge this PR)