TINKERPOP-1710: Add a note on tree() by-modulation and uniqueness of tree branches.#648
Merged
TINKERPOP-1710: Add a note on tree() by-modulation and uniqueness of tree branches.#648
Conversation
…at happens when duplicate nodes are realized in a tree projection.
Contributor
|
Travis sure is finicky today with time based tests, doc update looks good. VOTE: +1 |
Contributor
|
VOTE +1 |
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
https://issues.apache.org/jira/browse/TINKERPOP-1710
There was confusion as to what should happen what
tree()sees duplicate objects in the same depth of the tree. The behavior is as expected and not a "bug." Tree is constructed using path objects that are "horizontally" linked. If two objects are the same at the same depth, then they are merged into one none in the tree data structure.VOTE +1