Uh oh!
There was an error while loading. Please reload this page.
[refactor](nereids)align node id in explain with nereids node id #25068 - #25407
Merged
Conversation
xiaokang
commented
Oct 13, 2023
Contributor
run buildall |
hello-stephen
commented
Oct 13, 2023
Contributor
(From new machine)TeamCity pipeline, clickbench performance test result: |
it is painful to align node in `explain` and node in `explain physical plan`, since they use two different sets of node IDs. This pr makes 'explain' command use node IDs of their correspond node in 'explain physical plan' (cherry picked from commit ffaa145)
engleflyforce-pushed
the
25068-branch-2.0
branch
from
October 13, 2023 10:41
f29557d to
d70ed56Compareenglefly
commented
Oct 13, 2023
ContributorAuthor
run buildall |
This file contains hidden or 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
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Proposed changes
cherry pick pr 25068 for branch 2.0
Issue Number: close #xxx
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...