Uh oh!
There was an error while loading. Please reload this page.
[opt](nereids) infer in-predicate from or-predicate - #46468
Merged
Conversation
hello-stephen
commented
Jan 6, 2025
Contributor
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
englefly
commented
Jan 6, 2025
ContributorAuthor
run buildall |
doris-robot
commented
Jan 6, 2025
TPC-H: Total hot run time: 32462 ms |
doris-robot
commented
Jan 6, 2025
TPC-DS: Total hot run time: 190911 ms |
doris-robot
commented
Jan 6, 2025
ClickBench: Total hot run time: 31.09 s |
englefly
commented
Jan 7, 2025
ContributorAuthor
run buildall |
doris-robot
commented
Jan 7, 2025
TPC-H: Total hot run time: 32809 ms |
doris-robot
commented
Jan 7, 2025
TPC-DS: Total hot run time: 197193 ms |
doris-robot
commented
Jan 7, 2025
ClickBench: Total hot run time: 31.16 s |
englefly
commented
Jan 8, 2025
ContributorAuthor
run p0 |
starocean999
previously approved these changes
Jan 8, 2025
Contributor
PR approved by at least one committer and no changes requested. |
Contributor
PR approved by anyone and no changes requested. |
yujun777
reviewed
Jan 8, 2025
Uh oh!
There was an error while loading. Please reload this page.
englefly
commented
Jan 8, 2025
ContributorAuthor
run buildall |
yujun777
reviewed
Jan 8, 2025
Uh oh!
There was an error while loading. Please reload this page.
englefly
commented
Jan 8, 2025
ContributorAuthor
run buildall |
yujun777
self-requested a review
January 8, 2025 06:58
doris-robot
commented
Jan 8, 2025
TPC-H: Total hot run time: 32843 ms |
doris-robot
commented
Jan 8, 2025
TPC-DS: Total hot run time: 194895 ms |
doris-robot
commented
Jan 8, 2025
ClickBench: Total hot run time: 32.15 s |
englefly
commented
Jan 8, 2025
ContributorAuthor
run p0 |
englefly
commented
Jan 8, 2025
ContributorAuthor
run cloud_p0 |
englefly
commented
Jan 8, 2025
ContributorAuthor
run p0 |
2 similar comments
englefly
commented
Jan 8, 2025
ContributorAuthor
run p0 |
englefly
commented
Jan 9, 2025
ContributorAuthor
run p0 |
englefly
commented
Jan 9, 2025
ContributorAuthor
run buildall |
doris-robot
commented
Jan 9, 2025
TPC-H: Total hot run time: 33323 ms |
doris-robot
commented
Jan 9, 2025
TPC-DS: Total hot run time: 194787 ms |
doris-robot
commented
Jan 9, 2025
ClickBench: Total hot run time: 31.37 s |
starocean999
approved these changes
Jan 9, 2025
Contributor
PR approved by at least one committer and no changes requested. |
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?
previous verion has follow drawbacks
in order to solve above issues, we implemented a new version
first, it is a plan node level rule to avoid to be applied to the same expression repeatedly
second, we define replace mode and extract mode. if in replace mode, the original expression should be equivalent to the inferred in-pred, which is used for all plan node's expressions except filter.
for example, orig = "(a=1 and b=1) or (a=2 and c=2)" is equivalent to "a in (1, 2) and (a=1 and b=1) or (a=2 and c=2)".
orig is a filter condition, "a in (1, 2)" can be pushed down to storage layer, and this infer is useful. But if this is orig is an other join condition, this inferrence is useless. So in extract mode, "a in (1, 2)" is inferred, but in replace mode, it is not.
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)