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

br: handle special character in SQL. #37469

Closed
3pointer opened this issue Aug 30, 2022 · 4 comments · Fixed by #37486
Closed

br: handle special character in SQL. #37469

3pointer opened this issue Aug 30, 2022 · 4 comments · Fixed by #37486
Assignees
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
Copy link
Contributor

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

@3pointer 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
@3pointer
Copy link
Contributor Author

we need replace (+) before this.

storageURL, err := url.Parse(s.Storage)

@MoCuishle28
Copy link
Contributor

/assign MoCuishle28

@MoCuishle28
Copy link
Contributor

/severity minor

@MoCuishle28
Copy link
Contributor

/component br

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.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants