-
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: display cop tasks when explain format is "dot" #12225
Conversation
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.
Could you add a unit test? BTW, CI is failed.
Ok, I add it now. |
Codecov Report
@@ Coverage Diff @@
## master #12225 +/- ##
=========================================
Coverage 81.115% 81.115%
=========================================
Files 454 454
Lines 98634 98634
=========================================
Hits 80007 80007
Misses 12865 12865
Partials 5762 5762 |
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
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
Your auto merge job has been accepted, waiting for 12250 |
/run-all-tests |
cherry pick to release-2.1 failed |
cherry pick to release-3.1 failed |
It seems that, not for sure, we failed to cherry-pick this commit to release-2.1 release-3.0. Please comment '/run-cherry-picker' to try to trigger the cherry-picker if we did fail to cherry-pick this commit before. @zz-jason PTAL. |
@hailanwhu Could you help us to cherry-pick this PR to release 3.0, release 3.1 and release 2.1? |
/run-cherry-picker |
Signed-off-by: sre-bot <sre-bot@pingcap.com>
cherry pick to release-2.1 in PR #16121 |
Signed-off-by: sre-bot <sre-bot@pingcap.com>
cherry pick to release-3.0 in PR #16124 |
Signed-off-by: sre-bot <sre-bot@pingcap.com>
cherry pick to release-3.1 in PR #16125 |
What problem does this PR solve?
(1) In the physical plan tree, if the top node is a
TableReader
/IndexLookUpReader
/IndexReader
, it will not display the cop processes when executingexplain format="dot"
.(2) Some uses of
fmt.Sprintf
are not the best way.What is changed and how it works?
Check List
Tests
(1)
create table t(a int, b int, c int);
(2)
explain format="dot" select * from t where a < 2;
Code changes
planner/core/common_plan.go prepareTaskDot()