-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
[enhance](mtmv)refresh hms table before run mtmv task #38212
Conversation
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
run buildall |
TPC-H: Total hot run time: 40068 ms
|
TPC-DS: Total hot run time: 173119 ms
|
ClickBench: Total hot run time: 31.05 s
|
run buildall |
TPC-H: Total hot run time: 40036 ms
|
TPC-DS: Total hot run time: 172791 ms
|
ClickBench: Total hot run time: 30.3 s
|
run buildall |
TPC-H: Total hot run time: 42115 ms
|
TPC-DS: Total hot run time: 169386 ms
|
ClickBench: Total hot run time: 30.44 s
|
@@ -157,9 +148,6 @@ suite("test_hive_refresh_mtmv", "p0,external,hive,external_docker,external_docke | |||
""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
after refresh materialized view, maybe we should add order_qt
to check the mv result is right or not
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
There are some caches in the HMS catalog, which can result in the inability to maintain consistency with Hive side data even after a successful refresh of the materialized view. In this PR, the cache of relevant HMS tables will be cleared before refreshing the materialized view to solve this problem
There are some caches in the HMS catalog, which can result in the inability to maintain consistency with Hive side data even after a successful refresh of the materialized view. In this PR, the cache of relevant HMS tables will be cleared before refreshing the materialized view to solve this problem
There are some caches in the HMS catalog, which can result in the inability to maintain consistency with Hive side data even after a successful refresh of the materialized view.
In this PR, the cache of relevant HMS tables will be cleared before refreshing the materialized view to solve this problem