-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
executor: fix load data deal with escape character. (#16340) #16633
executor: fix load data deal with escape character. (#16340) #16633
Conversation
/run-all-tests |
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
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
/merge |
Sorry @cfzjywxk, you don't have permission to trigger auto merge event on this branch. |
/merge |
/run-all-tests |
@sre-bot merge failed. |
cherry-pick #16340 to release-3.0
What problem does this PR solve?
According to mysql document, the escaped character is interpreted as if it was not escaped. For example, \x is just x. When TiDB load data interpreting escaped, it ignore following character, just deal with character like
\t
.What is changed and how it works?
If the escaped character is interpreted as if it was not escaped, output the original character. For example:
9002 tab\ tab
will be interpreted as:
9002 tab tab
Related changes
Check List
Tests
Side effects
Release note