Skip to content
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

expression: split isTrue and isFalse expression sig (#16542) #16626

Closed

Conversation

sre-bot
Copy link
Contributor

@sre-bot sre-bot commented Apr 20, 2020

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 and isFalse is not pushed down correctly.
After an offline discussion with @XuHuaiyu @SunRunAway @breeswish , we decided to eliminate the keepNull variable by splitting the isTrue and isFalse expression sig to solve this problem.

What is changed and how it works?

Split the isTrue and isFalse expression sig. When the keepNull = true, we set setPbCode = tipb.ScalarFuncSig_XXXIsTrueWithNull. When the keepNull = false, we set setPbCode = tipb.ScalarFuncSig_XXXIsTrue.
So we can don't need to push down the keepNull variable.

Check List

Tests

  • Unit test
  • Integration test

@sre-bot
Copy link
Contributor Author

sre-bot commented Apr 20, 2020

/run-all-tests

@Reminiscent
Copy link
Contributor

Reminiscent commented Apr 21, 2020

wait for tipb#180 and tikv#7564

Copy link
Member

@zz-jason zz-jason left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Reminiscent please resolve conflict and fix CI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants