Uh oh!
There was an error while loading. Please reload this page.
[Improve](mtmv) skip the generation of invalid task for refresh mtmv - #46280
Merged
Conversation
hello-stephen
commented
Jan 2, 2025
Contributor
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
seawinde
reviewed
Jan 2, 2025
Uh oh!
There was an error while loading. Please reload this page.
doris-robot
commented
Jan 2, 2025
TPC-H: Total hot run time: 32659 ms |
doris-robot
commented
Jan 2, 2025
TPC-DS: Total hot run time: 191204 ms |
doris-robot
commented
Jan 2, 2025
ClickBench: Total hot run time: 31.97 s |
dqz123
commented
Jan 2, 2025
run buildall |
doris-robot
commented
Jan 2, 2025
TPC-H: Total hot run time: 33106 ms |
doris-robot
commented
Jan 2, 2025
TPC-DS: Total hot run time: 190859 ms |
doris-robot
commented
Jan 2, 2025
ClickBench: Total hot run time: 32 s |
zddr
reviewed
Jan 3, 2025
| AS select a.sid,b.cid,b.score from ${tblStu} a join ${tblGrade} b on a.sid = b.sid; | ||
| """ | ||
| sleep(1000) |
dqz123
commented
Jan 3, 2025
run buildall |
Contributor
PR approved by anyone and no changes requested. |
morrySnow
approved these changes
Jan 3, 2025
Contributor
PR approved by at least one committer and no changes requested. |
doris-robot
commented
Jan 3, 2025
TPC-H: Total hot run time: 32837 ms |
doris-robot
commented
Jan 3, 2025
TPC-DS: Total hot run time: 190341 ms |
doris-robot
commented
Jan 3, 2025
ClickBench: Total hot run time: 31.16 s |
github-actionsBot
pushed a commit
that referenced
this pull request
Jan 3, 2025
…#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>
github-actionsBot
pushed a commit
that referenced
this pull request
Jan 3, 2025
…#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>
yiguolei pushed a commit
that referenced
this pull request
Jan 4, 2025
…#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>
Closed
This file contains hidden or 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
Sign up for freeto 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.
What problem does this PR solve?
We specified the
excluded_trigger_tables = 'a'attribute when creating the materialized view. If tableais 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)