-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[Enhancement] Enable transparent union rewrite by default (backport #44764) #45586
Conversation
Signed-off-by: shuming.li <ming.moriarty@gmail.com> (cherry picked from commit 38aad60) # Conflicts: # test/sql/test_materialized_view/R/test_mv_partition_compensate_iceberg_part1 # test/sql/test_materialized_view/R/test_mv_partition_compensate_iceberg_part2 # test/sql/test_materialized_view/R/test_mv_partition_union_rewrite_mode_iceberg # test/sql/test_materialized_view/T/test_mv_partition_compensate_iceberg_part1 # test/sql/test_materialized_view/T/test_mv_partition_union_rewrite_mode_iceberg # test/sql/test_transparent_mv/R/test_transparent_mv_hive # test/sql/test_transparent_mv/T/test_transparent_mv_hive
Cherry-pick of 38aad60 has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
@mergify[bot]: Backport conflict, please reslove the conflict and resubmit the pr |
Quality Gate passedIssues Measures |
Why I'm doing:
Since we have supportted transparent mv(#42541 and #43304), we can treat a mv as always-consistent, and no need consider its freshness since the mv self will union refreshed data and no-refresh data.
For mv union rewrite, we can also no need consider mv's refreshness either.
eg:
test_mv1
can be used for mv rewrite whenever it's updated or not.What I'm doing:
TRANSPARENT
from UnionRewriteMode to SessionVariable since transaprent rewrite can be used associated with other union rewrite mode.explain costs
bugs if final tree containsPhysicalProject
.Further
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:
This is an automatic backport of pull request #44764 done by [Mergify](https://mergify.com). ## Why I'm doing:
Since we have supportted transparent mv(#42541 and #43304), we can treat a mv as always-consistent, and no need consider its freshness since the mv self will union refreshed data and no-refresh data.
For mv union rewrite, we can also no need consider mv's refreshness either.
eg:
test_mv1
can be used for mv rewrite whenever it's updated or not.What I'm doing:
TRANSPARENT
from UnionRewriteMode to SessionVariable since transaprent rewrite can be used associated with other union rewrite mode.explain costs
bugs if final tree containsPhysicalProject
.Further
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: