-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[BugFix] Add enable_active_materialized_view_schema_strict_check config to decide whether to check schema strictlly in activing mv #50869
Merged
LiShuMing
merged 2 commits into
StarRocks:main
from
LiShuMing:fix/main/fix_mv_active_strict_check
Sep 18, 2024
Merged
[BugFix] Add enable_active_materialized_view_schema_strict_check config to decide whether to check schema strictlly in activing mv #50869
LiShuMing
merged 2 commits into
StarRocks:main
from
LiShuMing:fix/main/fix_mv_active_strict_check
Sep 18, 2024
Conversation
This file contains 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
LiShuMing
force-pushed
the
fix/main/fix_mv_active_strict_check
branch
from
September 9, 2024 12:04
550a3c5
to
a6c55a7
Compare
satanson
approved these changes
Sep 10, 2024
@mergify rebase |
✅ Branch has been successfully rebased |
LiShuMing
force-pushed
the
fix/main/fix_mv_active_strict_check
branch
from
September 14, 2024 08:19
438415f
to
90270dc
Compare
@mergify rebase |
…ide whether to check schema strictlly in activing mv Signed-off-by: shuming.li <[email protected]>
Signed-off-by: shuming.li <[email protected]>
LiShuMing
force-pushed
the
fix/main/fix_mv_active_strict_check
branch
from
September 17, 2024 13:23
90270dc
to
0ac20b4
Compare
✅ Branch has been successfully rebased |
Quality Gate passedIssues Measures |
[Java-Extensions Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
[FE Incremental Coverage Report]✅ pass : 13 / 14 (92.86%) file detail
|
[BE Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
HangyuanLiu
approved these changes
Sep 18, 2024
@Mergifyio backport branch-3.3 |
✅ Backports have been created
|
mergify bot
pushed a commit
that referenced
this pull request
Sep 18, 2024
…ig to decide whether to check schema strictlly in activing mv (#50869) Signed-off-by: shuming.li <[email protected]> (cherry picked from commit d4add5c)
42 tasks
wanpengfei-git
pushed a commit
that referenced
this pull request
Sep 18, 2024
…ig to decide whether to check schema strictlly in activing mv (backport #50869) (#51117) Co-authored-by: shuming.li <[email protected]>
renzhimin7
pushed a commit
to renzhimin7/starrocks
that referenced
this pull request
Nov 7, 2024
…ig to decide whether to check schema strictlly in activing mv (StarRocks#50869) Signed-off-by: shuming.li <[email protected]> Signed-off-by: zhiminr.ren <[email protected]>
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.
Why I'm doing:
What I'm doing:
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check: