replace on old format row with new collation make prefix secondary index inconsistent

[wjhuang2016]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

log6.sql.zip
source log6.sql;
admin check table tbl_2;

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

No error.

3. What did you see instead (Required)

mysql> admin check table tbl_2;
ERROR 1105 (HY000): handle 13, index:types.Datum{k:0x5, decimal:0x0, length:0x0, i:0, collation:"binary", b:[]uint8{0x6c, 0x77}, x:interface {}(nil)} != record:<nil>

4. What is your TiDB version? (Required)

master, fresh build.

[lysu]

min reproduce script

start a cluster with new collation enabled

need set global tidb_row_format_version=1 and reconnect (need old row format, so need real tikv instead of unistore)

drop table if exists t;
create table t(c1 int primary key, c3 text, key idx1(c3(5)))collate utf8_unicode_ci;
insert into t select 1, 'V';
replace into t(c1, c3) values (1, 'rOCRvfiJi');
admin check table t;

it require:

• new collation
• prefix index
• old row format

not require:

• clustered index

so it maybe also affect on 4.0

[ti-srebot]

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