-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
Wrong hash key constructed for hash join #48991
Labels
affects-6.1
This bug affects the 6.1.x(LTS) versions.
affects-6.5
This bug affects the 6.5.x(LTS) versions.
affects-7.1
This bug affects the 7.1.x(LTS) versions.
affects-7.5
This bug affects the 7.5.x(LTS) versions.
severity/major
sig/execution
SIG execution
sig/planner
SIG: Planner
type/bug
The issue is confirmed as a bug.
Comments
@seiya-annie Could you give a more specific reproduction step? The current description is too little. |
The select should return 3 rows |
13 tasks
13 tasks
This was referenced Nov 30, 2023
13 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-6.1
This bug affects the 6.1.x(LTS) versions.
affects-6.5
This bug affects the 6.5.x(LTS) versions.
affects-7.1
This bug affects the 7.1.x(LTS) versions.
affects-7.5
This bug affects the 7.5.x(LTS) versions.
severity/major
sig/execution
SIG execution
sig/planner
SIG: Planner
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)
tidb-a: Nontransactional-Delete
tidb-b: normal-delete
execute same dml sql, and check with
"select * from tbl_3 order by col_11,col_12,col_13,col_14,col_15"
2. What did you expect to see? (Required)
results are same in tidb-a and tidb-b clusters
3. What did you see instead (Required)
The text was updated successfully, but these errors were encountered: