-
Notifications
You must be signed in to change notification settings - Fork 247
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
Fix read from range column partition table error (#2639) #2657
Fix read from range column partition table error (#2639) #2657
Conversation
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/run-all-tests |
2 similar comments
/run-all-tests |
/run-all-tests |
/merge |
@shiyuhang0: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: ad732dd
|
This is an automated cherry-pick of #2639
What problem does this PR solve?
close #2638
What is changed and how it works?
Fix the output of explain: TiSpark no more throw
NoSuchElementException
when there is no partition after partition prune.Fix the part of the bug that no partitions will be selected in the range column partition table.
TiSpark will contain
''
when generates partition exprs. For example, if your DDL isPARTITION p1 VALUES LESS THAN ('CN001')
, you will get something like${column_name} less than "'CN001'"
. Then, your filter can not match the partition exprs.After Fix, TiSpark will convert