-
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
planner: fix RANGE COLUMNS partition prune gives wrong result with special collation (#57344) #57406
planner: fix RANGE COLUMNS partition prune gives wrong result with special collation (#57344) #57406
Conversation
Signed-off-by: ti-chi-bot <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## release-7.5 #57406 +/- ##
================================================
Coverage ? 72.2038%
================================================
Files ? 1415
Lines ? 412783
Branches ? 0
================================================
Hits ? 298045
Misses ? 94796
Partials ? 19942
Flags with carried forward coverage won't be shown. Click here to find out more.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Defined2014, qw4990 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
/retest |
This is an automated cherry-pick of #57344
What problem does this PR solve?
Issue Number: close #57261
Problem Summary: Don't use
sortKey
to do partition prune.What changed and how does it work?
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.