-
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, executor: allow build root task type of expand operator and implement expand executor #54536
Conversation
Hi @AilinKid. Thanks for your PR. PRs from untrusted users cannot be marked as trusted with I understand the commands that are listed here. 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 kubernetes-sigs/prow repository. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #54536 +/- ##
=================================================
- Coverage 72.7920% 56.8239% -15.9681%
=================================================
Files 1551 1682 +131
Lines 436754 628114 +191360
=================================================
+ Hits 317922 356919 +38997
- Misses 99241 247552 +148311
- Partials 19591 23643 +4052
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Signed-off-by: AilinKid <314806019@qq.com>
Signed-off-by: AilinKid <314806019@qq.com>
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.
LGTM
// for property.RootTaskType and property.MppTaskType with no partition option, we can give an MPP Expand. | ||
if p.SCtx().GetSessionVars().IsMPPAllowed() { | ||
canPushToTiFlash := p.CanPushToCop(kv.TiFlash) |
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.
"CanPushToCop" This function name is strange. Cop is a protocol name but TiFlash already deprecated TiFlashCop and only keep the TiFlash[MPP]
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.
yes, borrowed from old logic, i think it should be renamed as p.CanPushToEngine, since your argument is engine type, the name will be more accurate.
return nil, true, nil | ||
// for property.RootTaskType, we can give a TiDB Expand. | ||
{ | ||
taskTypes := []property.TaskType{property.CopSingleReadTaskType, property.CopMultiReadTaskType, property.RootTaskType} |
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.
Do we need to keep all taskTypes in here? Because there is only expand operator in tidb, so why we still need to keep copsingle and copmulti?
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.
when we come here, the prop asks for a root expand execution, while for its children prop, there is no limitation here.
Expand(Root)
+ IndexReader( from single cop prop)
+ IndexRangeScan
Expand(Root)
+ IndexLookupReader (from multi cop prop)
+ IndexRangeScan
+ TiDBRowIDScan
Expand(Root)
+ OtherRootOp(Root) (from root prop)
+ OtherOps
Expand(Root)
+ OtherMppOps (Mpp) (from mpp prop)
+ OtherOps
the four cases here are all reasonable
Co-authored-by: Elsa <111482174+elsa0520@users.noreply.github.com>
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.
LGTM
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: elsa0520, windtalker 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:
|
@AilinKid: The following test failed, say
Full PR test history. Your PR dashboard. 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 kubernetes-sigs/prow repository. I understand the commands that are listed here. |
/retest-required |
@AilinKid: Cannot trigger testing until a trusted user reviews the PR and leaves an 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 kubernetes-sigs/prow repository. |
What problem does this PR solve?
Issue Number: close #42631
Problem Summary:
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.