[ 
https://issues.apache.org/jira/browse/TINKERPOP-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070573#comment-16070573
 ] 

ASF GitHub Bot commented on TINKERPOP-1710:
-------------------------------------------

GitHub user okram opened a pull request:

    https://github.com/apache/tinkerpop/pull/648

    TINKERPOP-1710: Add a note on tree() by-modulation and uniqueness of tree 
branches.

    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

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apache/tinkerpop TINKERPOP-1710

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/tinkerpop/pull/648.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #648
    
----
commit e962f5964f59f116f58c3294f38ac5c4904732e9
Author: Marko A. Rodriguez <[email protected]>
Date:   2017-06-30T18:48:35Z

    added a tree() example to the docs to clear up any confusion about what 
happens when duplicate nodes are realized in a tree projection.

----


> Add a note on tree() by-modulation and uniqueness of tree branches.
> -------------------------------------------------------------------
>
>                 Key: TINKERPOP-1710
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1710
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 3.2.5
>            Reporter: Marko A. Rodriguez
>            Assignee: Marko A. Rodriguez
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to