-
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
util/ranger: Handle boundary value correctly in ranger to avoid incorrect tableDual plan (#52225) #53320
util/ranger: Handle boundary value correctly in ranger to avoid incorrect tableDual plan (#52225) #53320
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## release-7.1 #53320 +/- ##
================================================
Coverage ? 73.4510%
================================================
Files ? 1211
Lines ? 380162
Branches ? 0
================================================
Hits ? 279233
Misses ? 83114
Partials ? 17815 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hawkingrei, wjhuang2016 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 #52225
What problem does this PR solve?
Issue Number: close #50051
Problem Summary:
The function
excludeToIncludeForIntPoint
should deal with the boundary value correctly.What changed and how does it work?
I guess it is not a bad idea to change the type of the point in this case.
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.