[
https://issues.apache.org/jira/browse/TINKERPOP-968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136454#comment-15136454
]
Marko A. Rodriguez commented on TINKERPOP-968:
----------------------------------------------
Why {{limit(1)}}? Look how {{MapStep}} works vs. {{FilterStep}}. One splits to
a new child, while the other passes through. If {{limit(1)}} works, then you
think, is this expensive? Yes, {{limit(1)}} is expensive. Find a
{{SideEffectStep}} or {{FilterStep}} that is crazy cheap and serializable (no
closures). Ah, but {{colesce()}} is a {{FlatMapStep}}... hmmm.... keep thinking.
> 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)
