-
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
strange plan for "not(not())" and "< " condition without projection cause tikv copr error #25727
Comments
@winoros please help take look or distribute to others guys thx~ :) |
The merge result of So the expr is correct |
The column |
/assign |
@lysu I cannot reproduce the error. Could you please check whether the bug still exists, thx~ |
yes it seems be same as #27245 already fixed by @wjhuang2016 in master and 5.1, but 5.1 ... |
Please edit this comment or add a new comment to complete the following informationNot a bug
Duplicate bug
BugNote: Make Sure that 'component', and 'severity' labels are added 1. Root Cause Analysis (RCA) (optional)2. Symptom (optional)3. All Trigger Conditions (optional)4. Workaround (optional)5. Affected versions6. Fixed versions |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
then exec SQL with the empty table
2. What did you expect to see? (Required)
success
3. What did you see instead (Required)
fail with tikv cop error
plan seems be very stranger
but if we change SQL to delete some column in the projection, it will work
4. What is your TiDB version? (Required)
85dee1d
The text was updated successfully, but these errors were encountered: