-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[fix](orc) check all the cases before build_search_argument #44615
[fix](orc) check all the cases before build_search_argument #44615
Conversation
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
run buildall |
TPC-H: Total hot run time: 39864 ms
|
TPC-DS: Total hot run time: 197432 ms
|
ClickBench: Total hot run time: 32.52 s
|
TeamCity be ut coverage result: |
run buildall |
d2d6724
to
f06e0b5
Compare
run buildall |
TPC-H: Total hot run time: 39745 ms
|
TeamCity be ut coverage result: |
TPC-DS: Total hot run time: 197189 ms
|
ClickBench: Total hot run time: 33.08 s
|
run external |
run buildall |
TeamCity be ut coverage result: |
TPC-H: Total hot run time: 39882 ms
|
TPC-DS: Total hot run time: 196808 ms
|
ClickBench: Total hot run time: 33.13 s
|
Co-authored-by: Mingyu Chen (Rayner) <[email protected]>
TPC-H: Total hot run time: 39805 ms
|
TeamCity be ut coverage result: |
TPC-DS: Total hot run time: 190650 ms
|
ClickBench: Total hot run time: 33.12 s
|
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
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
…4615) In the old logic, the `check_expr_can_push_down` function does not check whether the `orc::Literal` are constructed successfully, but only checks during `build_search_argument`. However, if it is found that the `orc::Literal` fails to be constructed after `builder->startNot`, it will fail because the builder cannot end `startNot`. Therefore, we advance the behavior of constructing `orc::Literal` to the `check_expr_can_push_down` function and save the result to the map, so that it will never fail in the `build_search_argument` phase. Related PR: apache#43255
…44802) cherry-pick #44615 Co-authored-by: Socrates <[email protected]>
…44801) cherry-pick #44615 Co-authored-by: Socrates <[email protected]>
…pache#44615) (apache#44801)" This reverts commit 4b15b1f.
What problem does this PR solve?
In the old logic, the
check_expr_can_push_down
function does not check whether theorc::Literal
are constructed successfully, but only checks duringbuild_search_argument
. However, if it is found that theorc::Literal
fails to be constructed afterbuilder->startNot
, it will fail because the builder cannot endstartNot
.Therefore, we advance the behavior of constructing
orc::Literal
to thecheck_expr_can_push_down
function and save the result to the map, so that it will never fail in thebuild_search_argument
phase.Related PR: #43255
Problem Summary:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)