You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Marko A. Rodriguez (JIRA)" <ji...@apache.org> on 2015/11/23 20:19:11 UTC

[jira] [Commented] (TINKERPOP3-968) Add first class support for an optional traversal

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

Marko A. Rodriguez commented on TINKERPOP3-968:
-----------------------------------------------

Can you provide a recommendation for how this should look? Including [~dkuppitz] in this ticket as he has an eye for the Gremlin syntax.

> Add first class support for an optional traversal
> -------------------------------------------------
>
>                 Key: TINKERPOP3-968
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-968
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.1.0-incubating
>            Reporter: pieter martin
>
> Both SparQL and Cypher use the "Optional" keyword to indicate an optional traversal. SQL uses the "left join".
> Gremlin has no first class support for an optional traversal. It can be achieved with the choose step but it is verbose, unintuitive and not what the choose step is intended for.
> The benefits of optional traversals are many. In particular it makes it trivial to load complete subgraphs/trees with one easy to read intuitive gremlin statement.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)