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

INSERT ODKU EncodeRow error: data and columnID count not match #33608

Closed
mjonss opened this issue Mar 30, 2022 · 2 comments · Fixed by #33656
Closed

INSERT ODKU EncodeRow error: data and columnID count not match #33608

mjonss opened this issue Mar 30, 2022 · 2 comments · Fixed by #33656
Assignees
Labels
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. affects-5.4 This bug affects the 5.4.x(LTS) versions. affects-6.0 affects-6.1 This bug affects the 6.1.x(LTS) versions. severity/major sig/transaction SIG:Transaction type/bug The issue is confirmed as a bug.

Comments

@mjonss
Copy link
Contributor

mjonss commented Mar 30, 2022

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

Start tidb with binlog (like tiup playground nightly --db 1 --drainer 1 --kv 1 --pd 1 --pump 1 --ticdc 1)
Same test as in TestInsertOnDuplicateKey unit test:

create table a (x int primary key);
create table b (x int, y int);
insert into a values (1);
insert into b values (1, 2);
insert into a select x from b on duplicate key update a.x = b.y;

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

Succeeded update.

3. What did you see instead (Required)

tidb> insert into a select x from b on duplicate key update a.x = b.y;
ERROR 1105 (HY000): EncodeRow error: data and columnID count not match 2 vs 1

4. What is your TiDB version? (Required)

Release Version: v6.1.0-alpha
Edition: Community
Git Commit Hash: af6f4ea3c98f52d8c56646b226d720fc50a3314c
Git Branch: heads/refs/tags/v6.1.0-alpha
UTC Build Time: 2022-03-26 18:03:22
GoVersion: go1.18
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false
@mjonss mjonss added the type/bug The issue is confirmed as a bug. label Mar 30, 2022
@ti-chi-bot ti-chi-bot added may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.0 labels Mar 31, 2022
@zanmato1984 zanmato1984 added sig/transaction SIG:Transaction and removed sig/execution SIG execution labels May 3, 2022
@VelocityLight VelocityLight added the affects-6.1 This bug affects the 6.1.x(LTS) versions. label May 20, 2022
@tiancaiamao tiancaiamao added 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. affects-5.4 This bug affects the 5.4.x(LTS) versions. affects-6.0 affects-5.0 This bug affects 5.0.x versions. and removed may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.0 may-affects-5.0 This bug maybe affects 5.0.x versions. labels Jun 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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. affects-5.4 This bug affects the 5.4.x(LTS) versions. affects-6.0 affects-6.1 This bug affects the 6.1.x(LTS) versions. severity/major sig/transaction SIG:Transaction type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants