[
https://issues.apache.org/jira/browse/TINKERPOP3-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
pieter martin updated TINKERPOP3-968:
-------------------------------------
Description:
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.
was:
Both SparkQL 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.
> 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.1-incubating
> Reporter: pieter martin
> Assignee: Marko A. Rodriguez
> Labels: features
>
> 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)
