-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Internal error: UnionExec chunk column count mismatch #26554
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.
severity/major
sig/execution
SIG execution
type/bug
The issue is confirmed as a bug.
Comments
ChenPeng2013
added
type/bug
The issue is confirmed as a bug.
sig/execution
SIG execution
severity/major
labels
Jul 26, 2021
Closed
a smaller reproduction: CREATE TABLE t (
a int,
b int
)
PARTITION BY HASH( a )
PARTITIONS 2;
insert into t values(1,2);
select * from t where b = 2 and b in (select b from t);
It seems that |
|
Release 4.0 also has this problem, but doesn't throw error. Lines 1617 to 1620 in 880c9b5
|
12 tasks
This was referenced Sep 5, 2021
Please check whether the issue should be labeled with 'affects-x.y' or 'backport-x.y.z', |
This was referenced Sep 6, 2021
time-and-fate
added
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.
labels
Dec 20, 2021
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.
severity/major
sig/execution
SIG execution
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
2. What did you expect to see? (Required)
3. What did you see instead (Required)
4. What is your TiDB version? (Required)
It can be reproduced on branch release-5.0, release-5.1 and master
The release-4.0 branch doesn't have the issue
The text was updated successfully, but these errors were encountered: