-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[opt](optimizer)force join commute optimize even memoMaxGroupExpressionSize exceed #58746
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
base: master
Are you sure you want to change the base?
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
1 similar comment
|
run buildall |
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
FE UT Coverage ReportIncrement line coverage |
TPC-H: Total hot run time: 34749 ms |
TPC-DS: Total hot run time: 180121 ms |
ClickBench: Total hot run time: 27.2 s |
FE Regression Coverage ReportIncrement line coverage |
|
run buildall |
TPC-H: Total hot run time: 35012 ms |
TPC-DS: Total hot run time: 178096 ms |
ClickBench: Total hot run time: 27.27 s |
FE Regression Coverage ReportIncrement line coverage |
1 similar comment
FE Regression Coverage ReportIncrement line coverage |
|
run feut |
|
run nonConcurrent |
FE UT Coverage ReportIncrement line coverage |
d66174e to
198ad67
Compare
|
PR approved by at least one committer and no changes requested. |
What problem does this PR solve?
when group expression number exceeds memoMaxGroupExpressionSize(currently 10000), we stop to exploration group exressions.
However, join-commute is too important for join. and hence, we allow JoinCommute optimization in this situation.
Issue 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)