-
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
Restore meet error: Unsupported collation when new collation is enabled: 'utf8mb4_0900_ai_ci' #39150
Labels
affects-6.0
affects-6.1
This bug affects the 6.1.x(LTS) versions.
affects-6.2
affects-6.3
affects-6.4
component/br
This issue is related to BR of TiDB.
severity/major
type/bug
The issue is confirmed as a bug.
Comments
/component br |
12 tasks
ti-chi-bot
pushed a commit
that referenced
this issue
Nov 22, 2022
Merged
12 tasks
12 tasks
ti-chi-bot
pushed a commit
that referenced
this issue
Nov 23, 2022
15 tasks
15 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-6.0
affects-6.1
This bug affects the 6.1.x(LTS) versions.
affects-6.2
affects-6.3
affects-6.4
component/br
This issue is related to BR of TiDB.
severity/major
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)
new_collations_enabled_on_first_bootstrap: false
.create table
books(
idbigint auto_increment,
namevarchar(64), primary key (
id)) CHARSET utf8mb4 COLLATE utf8mb4_0900_ai_ci;
new_collations_enabled_on_first_bootstrap: false
.2. What did you expect to see? (Required)
restore successfully
3. What did you see instead (Required)
restore failed with error
Error: [ddl:1273]Unsupported collation when new collation is enabled: 'utf8mb4_0900_ai_ci'
4. What is your TiDB version? (Required)
v6.1.0
The text was updated successfully, but these errors were encountered: