Open wjhuang2016 opened 7 months ago
Hi @wjhuang2016 I can not reproduce this bug in latest nightly version( 134d2bfbe0002b24177155873038188d4544e538), can you provide more information about this bug? For example, the query plan when for the panic execution?
@windtalker
Try it:
analyze table t6aa5c01d;
I can reproduce it after analyze, thanks.
It should be a bug in encoding, the index idx_7
contains 3 columns(col_10, col_6, col_9), but looks like if length(col_9) == 0, the decode result of the key contains only two column, which makes the error of index out of bound. I can't reproduce it in TiDB + TiKV cluster, so it seems a bug only in unistore.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
2. What did you expect to see? (Required)
No panic
3. What did you see instead (Required)
4. What is your TiDB version? (Required)
1fc92b32b05e3f2f04b9d321a9e224b9125a4a82