plan, expression: support is null
in hash partition pruning (#17281)
#17310
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.
cherry-pick #17281 to release-4.0
What problem does this PR solve?
Problem Summary:
SQL like
select * from t where a is null
will produce a full table scan plan in hash partition. For example:This SQL will produce following result:
What is changed and how it works?
Proposal: xxx
What's Changed:
During partition pruning, if a column is equal to
NULL
, all calculation relating to it will produce null result and set aNULL
flag.How it Works:
If pruning result with a
NULL
flag, it will be point top0
.Related changes
Check List
Tests
Side effects
Release note
is null
filter condition in hash partition pruning