-
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: fix space requirement when binding from history (#41140) #41244
planner: fix space requirement when binding from history (#41140) #41244
Conversation
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/hold high priority for trunk branch |
/unhold |
/retest |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: add218d
|
/retest |
This is an automated cherry-pick of #41140
What problem does this PR solve?
Issue Number: close #41126
Problem Summary:
The normalized sql from statement summary we used to parse is improper. Because for some builtin functions, there are space between the function name and parentheses, this will cause parser panic. For example
Here are some builtin functions from mysql that can't be parsed where there has space between the function name and parentheses
https://dev.mysql.com/doc/refman/8.0/en/function-resolution.html
What is changed and how it works?
We use the original sql instead
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.