planner: explain a physicalPlan with IndexMerge in "dot" format #12248
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## master #12248 +/- ##
================================================
- Coverage 81.1266% 81.1027% -0.0239%
================================================
Files 454 454
Lines 98811 98628 -183
================================================
- Hits 80162 79990 -172
+ Misses 12881 12874 -7
+ Partials 5768 5764 -4 |
zz-jason
added
sig/planner
zz-jason
changed the title
alivxxx
added
status/LGT2
|
/run-all-tests |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
After a physical plan with
IndexMergePathgenerated, it should be explained.What is changed and how it works?
Check List
Tests
Code changes
planner/core/common_plan.go prepareTaskDot()