[
https://issues.apache.org/jira/browse/TINKERPOP-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136451#comment-15136451
]
Marko A. Rodriguez edited comment on TINKERPOP-968 at 2/7/16 9:23 PM:
----------------------------------------------------------------------
I recommend you figure out how to express your query using {{GraphTraversal}}
steps. Once you get that, then the compilation will be obvious.
For instance, try {{coalesce(out('ab'),limit(1)))}}.
was (Author: okram):
I recommend you figure out how to express your query using {{GraphTraversal}}
steps. Once you get that, then the compilation will be obvious.
For instance, try {{coalesce(out('ab'),limit(0))}}.
> Add first class support for an optional traversal
> -------------------------------------------------
>
> Key: TINKERPOP-968
> URL: https://issues.apache.org/jira/browse/TINKERPOP-968
> Project: TinkerPop
> 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)
