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

copr: tikv crash when elt enum type #24479

Closed
wshwsh12 opened this issue May 8, 2021 · 1 comment · Fixed by tikv/tikv#10136
Closed

copr: tikv crash when elt enum type #24479

wshwsh12 opened this issue May 8, 2021 · 1 comment · Fixed by tikv/tikv#10136
Assignees
Labels
severity/critical type/bug The issue is confirmed as a bug.

Comments

@wshwsh12
Copy link
Contributor

wshwsh12 commented May 8, 2021

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

drop table t;
create table t(a enum("a"), b int);
insert into t values(1,1);
select * from t where elt(a,b);

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

MySQL [test]> select * from t where elt(a,b);
+------+------+
| a | b |
+------+------+
| a | 1 |
+------+------+
1 row in set (0.001 sec)

3. What did you see instead (Required)

ERROR 9002 (HY000): TiKV server timeout

4. What is your TiDB version? (Required)

Only master

@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
severity/critical type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants