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

Restore report Unsupported collation error #49466

Closed
3pointer opened this issue Dec 14, 2023 · 0 comments · Fixed by #49579
Closed

Restore report Unsupported collation error #49466

3pointer opened this issue Dec 14, 2023 · 0 comments · Fixed by #49579
Labels
affects-6.1 affects-6.5 affects-7.1 affects-7.5 component/br This issue is related to BR of TiDB. severity/major 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)

  1. create table with old collation such as utf8mb4_0900_ai_ci in v5.1 cluster.
  2. use v5.1 br to backup cluster.
  3. restore to v6.5 cluster which new_collations_enabled_on_first_bootstrap is set to false.

2. What did you expect to see? (Required)

restore success with --check-requirements=false

3. What did you see instead (Required)

[failed to restore"] [error="[ddl:1273]Unsupported collation when new collation is enabled: 'utf8mb4_0900_ai_ci'"

4. What is your TiDB version? (Required)

@3pointer 3pointer added type/bug The issue is confirmed as a bug. component/br This issue is related to BR of TiDB. labels Dec 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-6.1 affects-6.5 affects-7.1 affects-7.5 component/br This issue is related to BR of TiDB. severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants