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

"Data too long" error when dumping stats from a table with new collation #27024

Closed
time-and-fate opened this issue Aug 9, 2021 · 3 comments · Fixed by #27033
Closed

"Data too long" error when dumping stats from a table with new collation #27024

time-and-fate opened this issue Aug 9, 2021 · 3 comments · Fixed by #27033
Assignees
Labels
affects-4.0 This bug affects 4.0.x versions. affects-5.0 This bug affects 5.0.x versions. affects-5.1 This bug affects 5.1.x versions. affects-5.2 This bug affects 5.2.x versions. affects-5.3 This bug affects 5.3.x versions. component/statistics fixes-5.1.2 fixes-5.3.0 This bug is fixed at 5.3.0 severity/major sig/planner SIG: Planner type/bug This issue is a bug.

Comments

@time-and-fate
Copy link
Member

time-and-fate commented Aug 9, 2021

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

start a tidb with new collation enabled.

use test;
create table t(a varchar(10) collate utf8mb4_unicode_ci);
insert into t values('abcdefghij');
insert into t values('abcdefghnj');
analyze table t with 0 topn;

try to dump the stats:

http://127.0.0.1:10080/stats/dump/test/t

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

No error.

3. What did you see instead (Required)

"[types:1406]Data Too Long, field len 10, data len 20"

4. What is your TiDB version? (Required)

current master (af2da8d)

@time-and-fate time-and-fate added the type/bug This issue is a bug. label Aug 9, 2021
@time-and-fate
Copy link
Member Author

/sig planner
/component statistics

@time-and-fate
Copy link
Member Author

/assign time-and-fate

@github-actions github-actions bot added this to Issue Backlog: Need Triage in SIG Planner Kanban Aug 9, 2021
SIG Planner Kanban automation moved this from Issue Backlog: Need Triage to Coding Finished (This Week) Aug 17, 2021
@ti-srebot
Copy link
Contributor

Please edit this comment or add a new comment to complete the following information

Not a bug

  1. Remove the 'type/bug' label
  2. Add notes to indicate why it is not a bug

Duplicate bug

  1. Add the 'type/duplicate' label
  2. Add the link to the original bug

Bug

Note: Make Sure that 'component', and 'severity' labels are added
Example for how to fill out the template: #20100

1. Root Cause Analysis (RCA) (optional)

2. Symptom (optional)

3. All Trigger Conditions (optional)

4. Workaround (optional)

5. Affected versions

6. Fixed versions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-4.0 This bug affects 4.0.x versions. affects-5.0 This bug affects 5.0.x versions. affects-5.1 This bug affects 5.1.x versions. affects-5.2 This bug affects 5.2.x versions. affects-5.3 This bug affects 5.3.x versions. component/statistics fixes-5.1.2 fixes-5.3.0 This bug is fixed at 5.3.0 severity/major sig/planner SIG: Planner type/bug This issue is a bug.
Projects
No open projects
SIG Planner Kanban
  
Coding Finished (This Week)
5 participants