-
Notifications
You must be signed in to change notification settings - Fork 3.4k
[Improve](mtmv) skip the generation of invalid task for refresh mtmv #46280
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:
|
3451c20
to
3a9d13e
Compare
TPC-H: Total hot run time: 32659 ms
|
TPC-DS: Total hot run time: 191204 ms
|
ClickBench: Total hot run time: 31.97 s
|
run buildall |
TPC-H: Total hot run time: 33106 ms
|
TPC-DS: Total hot run time: 190859 ms
|
ClickBench: Total hot run time: 32 s
|
AS select a.sid,b.cid,b.score from ${tblStu} a join ${tblGrade} b on a.sid = b.sid; | ||
""" | ||
|
||
sleep(1000) |
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.
why sleep?
run buildall |
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.
LGTM
PR approved by anyone and no changes requested. |
PR approved by at least one committer and no changes requested. |
TPC-H: Total hot run time: 32837 ms
|
TPC-DS: Total hot run time: 190341 ms
|
ClickBench: Total hot run time: 31.16 s
|
…#46280) ### What problem does this PR solve? We specified the `excluded_trigger_tables = 'a'` attribute when creating the materialized view. If table `a` is updated frequently, many invalid tasks will be generated, and these tasks do not really refresh the mv, which is unreasonable, too many invalid tasks will wash away useful task information Co-authored-by: garenshi <garenshi@tencent.com>
…#46280) ### What problem does this PR solve? We specified the `excluded_trigger_tables = 'a'` attribute when creating the materialized view. If table `a` is updated frequently, many invalid tasks will be generated, and these tasks do not really refresh the mv, which is unreasonable, too many invalid tasks will wash away useful task information Co-authored-by: garenshi <garenshi@tencent.com>
…#46280) ### What problem does this PR solve? We specified the `excluded_trigger_tables = 'a'` attribute when creating the materialized view. If table `a` is updated frequently, many invalid tasks will be generated, and these tasks do not really refresh the mv, which is unreasonable, too many invalid tasks will wash away useful task information Co-authored-by: garenshi <garenshi@tencent.com>
What problem does this PR solve?
We specified the
excluded_trigger_tables = 'a'
attribute when creating the materialized view. If tablea
is updated frequently, many invalid tasks will be generated, and these tasks do not really refresh the mv, which is unreasonable, too many invalid tasks will wash away useful task informationIssue 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)