[
https://issues.apache.org/jira/browse/TINKERPOP-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16233681#comment-16233681
]
pieter martin commented on TINKERPOP-1822:
------------------------------------------
Perhaps this ticket could be generalized to all traversals.
My understanding is that TinkerPop has no specified semantics regarding DFS or
BFS. Traversals can be optimized and subtly change what a user might have
expected. As this is unspecified semantics different implementation can also
have different behavior based on their strategies. Even on TinkerGraph I'd say
most users can not upfront tell exactly how any particular traversal may be
optimized. Steps rewritten, barriers injected etc. If users want to have
reliable DFS/BFS semantics it should be specified.
Perhaps TinkerPop needs a first class notion of {{DFS/BFS/NONE}} which can be
properly specified and tested.
The default would be {{NONE}} like it is now with the implementation free to
optimize it in any way it sees fit.
How about using the existing {{OrderStep}}?
{{repeat(out().order(DFS))}}
> Repeat should depth first search
> --------------------------------
>
> Key: TINKERPOP-1822
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1822
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.3.0, 3.2.6
> Reporter: Robert Dale
> Priority: Major
>
> Perhaps optionally.
> See also:
> * https://groups.google.com/forum/#!topic/gremlin-users/gLSLxH_K-wE
> * https://github.com/apache/tinkerpop/pull/715
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
