-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[enhance](mtmv)Base table changes should not cause nested MTMV to schema change status #56244
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
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
FE Regression Coverage ReportIncrement line coverage |
|
run buildall |
FE UT Coverage ReportIncrement line coverage |
|
run performance |
FE Regression Coverage ReportIncrement line coverage |
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
…ema change status (#56244) t1 => mv1 => mv2 if t1 schema change status of mv1 should is schema change status of mv2 should is normal
…ot cause nested MTMV to schema change status apache#56244 (apache#5126) cherry-picks from apache#56244 Related to apache#4676 Co-authored-by: zhangdong <493738387@qq.com>
What problem does this PR solve?
t1 => mv1 => mv2
if t1 schema change
status of mv1 should is schema change
status of mv2 should is normal
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)