-
Notifications
You must be signed in to change notification settings - Fork 6.1k
ranger, core: Ranger changes to push #65980
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
base: master
Are you sure you want to change the base?
Conversation
|
Hi @wddevries, I noticed you mentioned me, but I couldn't find your Pantheon account linked to your GitHub account. Please connect your GitHub account to Pantheon first, and then try again. Thank you! Learn more about Pantheon AI |
|
Hi @wddevries. Thanks for your PR. PRs from untrusted users cannot be marked as trusted with I understand the commands that are listed here. DetailsInstructions 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 kubernetes-sigs/prow repository. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #65980 +/- ##
================================================
- Coverage 77.7818% 77.5191% -0.2628%
================================================
Files 2001 1923 -78
Lines 545618 537796 -7822
================================================
- Hits 424392 416895 -7497
- Misses 119564 120889 +1325
+ Partials 1662 12 -1650
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
|
@pantheon-bot please review. |
|
✅ Code looks good. No issues found. |
|
/ok-to-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This pull request cleans up and simplifies ranger code by removing duplicated logic and unused failpoints.
Changes:
- Refactored
getPotentialEqOrInColOffsetfunction inpkg/util/ranger/detacher.goto eliminate duplicated code branches and fix inconsistencies in column comparison logic - Removed unused
MockOnlyEnableIndexHashJoinfailpoint frompkg/planner/core/exhaust_physical_plans.go
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| pkg/util/ranger/detacher.go | Consolidated duplicated code in getPotentialEqOrInColOffset function, fixing bugs where one branch used EqualColumn instead of EqualByExprAndID and was missing null checks for ast.NullEQ |
| pkg/planner/core/exhaust_physical_plans.go | Removed three instances of unused MockOnlyEnableIndexHashJoin failpoint (replaced by MockOnlyEnableIndexHashJoinV2 in current codebase) |
henrybw
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, much simpler and easier to read now. Thanks for cleaning this up.
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: henrybw The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
What problem does this PR solve?
Issue Number: ref #65979
Problem Summary:
What changed and how does it work?
This pull request makes two changes:
getPotentialEqOrInColOffsetfunction has been removed, and the inconsistencies between the two versions have been removed.Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide (https://pingcap.github.io/tidb-dev-guide/contrbute-to-tidb/release-notes-style-guide.html) to write a quality release note.