-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
planner: let exists subquery return signed int type (#57277) #57365
planner: let exists subquery return signed int type (#57277) #57365
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## release-8.5 #57365 +/- ##
================================================
Coverage ? 56.4419%
================================================
Files ? 1780
Lines ? 635689
Branches ? 0
================================================
Hits ? 358795
Misses ? 252771
Partials ? 24123
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: AilinKid, windtalker The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
This is an automated cherry-pick of #57277
What problem does this PR solve?
Issue Number: close #56641
Problem Summary:
The root cause of #56641 is that
exists
subquery returns unsigned type in TiDB, and it is caused by thatin TiDB
expression.NewOne()
andexpression.NewZero()
both returns unsigned integer type.And in
tidb/pkg/planner/core/expression_rewriter.go
Lines 1105 to 1109 in 56e7093
It use
expression.NewOne()
andexpression.NewZero()
as the result of the exists subquery.The reason why
expression.NewOne()
andexpression.NewZero()
returns unsigned integer type is hard to tell now. The only thing I know is it is introduced in this pr: #21062 . Looks like it is not related to exists subquery.It may have high regression risk to change the return type of
expression.NewOne()
andexpression.NewZero()
, so this pr adds two new function to return signed version on constant one and constant zero.What changed and how does it work?
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.