expression: split isTrue and isFalse expression sig (#16542) #16626
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 #16542 to release-2.1
What problem does this PR solve?
Close: #15718
Close: #15987
Close: #16501
Related PR: #12173 #15926 tikv#7532
The reason for the above error is that the variable keepNull in the expression
isTrue
andisFalse
is not pushed down correctly.After an offline discussion with @XuHuaiyu @SunRunAway @breeswish , we decided to eliminate the
keepNull
variable by splitting theisTrue
andisFalse
expression sig to solve this problem.What is changed and how it works?
Split the
isTrue
andisFalse
expression sig. When thekeepNull = true
, we setsetPbCode = tipb.ScalarFuncSig_XXXIsTrueWithNull
. When thekeepNull = false
, we setsetPbCode = tipb.ScalarFuncSig_XXXIsTrue
.So we can don't need to push down the
keepNull
variable.Check List
Tests