-
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
br: handle special character in SQL. #37469
Labels
affects-5.4
This bug affects 5.4.x versions.
affects-6.1
component/br
This issue is related to BR of TiDB.
severity/minor
type/bug
The issue is confirmed as a bug.
Comments
3pointer
added
type/bug
The issue is confirmed as a bug.
affects-5.4
This bug affects 5.4.x versions.
affects-6.1
labels
Aug 30, 2022
we need replace (+) before this. Line 228 in 6ae88c4
|
/assign MoCuishle28 |
/severity minor |
12 tasks
/component br |
ti-chi-bot
pushed a commit
that referenced
this issue
Sep 6, 2022
This was referenced Sep 6, 2022
ti-chi-bot
pushed a commit
that referenced
this issue
Sep 16, 2022
ti-chi-bot
pushed a commit
that referenced
this issue
Oct 10, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-5.4
This bug affects 5.4.x versions.
affects-6.1
component/br
This issue is related to BR of TiDB.
severity/minor
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
In SQL backup/restore if sk has special character (+), we will encounter the error. just like pingcap/br#603, we handle it in binary. but the URL parsed before we replace it in SQL.
2. What did you expect to see? (Required)
success
3. What did you see instead (Required)
failed with SignatureDoesNotMatch.
4. What is your TiDB version? (Required)
v6.1.0
The text was updated successfully, but these errors were encountered: