[Fix](nereids) fix partition prune not expression compute logic #40619
Conversation
This file contains 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
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
|
run buildall |
Sign up for free
to 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.
In partition pruning, whether an expression supports NOT computation depends on the rejectNot boolean flag. If rejectNot is true, it indicates support for the computation. For example, consider partition column a with a range of (1,10) in partition1. For the expression NOT (a > 5), the computation process involves first evaluating a > 5. Combined with the partition range, this results in 5 < a < 10 for a > 5. Then, applying NOT (a > 5) leads to the range 1 < a <= 5 if rejectNot is true, meaning the calculation is valid.
However, this calculation should only be supported for certain operators like <, <=, >, >= and =. In this pull request (PR), the default value of rejectNot is set to false, reducing the range of expressions that support NOT computation. This change prevents unsupported expressions, such as LIKE, from producing incorrect results.