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

runtime error: index out of range [1] with length 1 #26779

Closed
ChenPeng2013 opened this issue Aug 2, 2021 · 3 comments
Closed

runtime error: index out of range [1] with length 1 #26779

ChenPeng2013 opened this issue Aug 2, 2021 · 3 comments
Assignees
Labels
severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.

Comments

@ChenPeng2013
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

using tikv store

use test;
source [test.txt](https://github.com/pingcap/tidb/files/6913910/test.txt)

select * from IDT_HP24100 where col1 is null and col2 = "ogbRo";

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

release-4.0 & release-5.1 & master

mysql> select * from IDT_HP24100 where col1 is null and col2 = "ogbRo";
Empty set (0.08 sec)

3. What did you see instead (Required)

release-5.0

mysql> select * from IDT_HP24100 where col1 is null and col2 = "ogbRo";
ERROR 1105 (HY000): runtime error: index out of range [1] with length 1

4. What is your TiDB version? (Required)

Release Version: v5.0.4
Edition: Community
Git Commit Hash: 48c4b91d5d7c8f4aca68fffcc9f320c9a6e4cce2
Git Branch: heads/refs/tags/v5.0.4
UTC Build Time: 2021-07-26 13:36:17
GoVersion: go1.13
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false
@ChenPeng2013 ChenPeng2013 added type/bug The issue is confirmed as a bug. sig/planner SIG: Planner severity/major labels Aug 2, 2021
@time-and-fate
Copy link
Member

Confirmed that this bug was fixed by #23849 on the master branch.
Cherry-picked to release-5.0 in #26963.

@ChenPeng2013
Copy link
Contributor Author

duplicated of #23802

@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/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

3 participants