add edge rank & fix test case #2337
Merged
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
nevermore3
requested review from
CPWstatic,
laura-ding,
Shylock-Hg and
yixinglu
laura-ding
approved these changes
Sep 4, 2020
CPWstatic
approved these changes
Sep 4, 2020
xuguruogu
pushed a commit
to xuguruogu/nebula
that referenced
this pull request
Sep 12, 2020
* add edge rank & fix test case * fix test error Co-authored-by: dutor <440396+dutor@users.noreply.github.com>
tong-hao
pushed a commit
to tong-hao/nebula
that referenced
this pull request
Jun 1, 2021
* add edge rank & fix test case * fix test error Co-authored-by: dutor <440396+dutor@users.noreply.github.com>
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 changes were proposed in this pull request?
add rank field to the test case
Why are the changes needed?
Avoid covering multiple edges of the same type
Will break the compatibility? How if so?
no
Does this PR introduce any user-facing change?
no
How was this patch tested?
Comparison with 2.0 test cases
Checklist