[
https://issues.apache.org/jira/browse/TINKERPOP3-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14637946#comment-14637946
]
Matt Frantz commented on TINKERPOP3-781:
----------------------------------------
I remember seeing that discussion, but I couldn't find the ticket. Interesting
workarounds. I'll give them a try.
I still think that the behavior described in this ticket is desirable because
it seems intuitive. However, if it doesn't make sense for some case that I
haven't considered, we could document it here.
> Local aggregation should not destroy path
> -----------------------------------------
>
> Key: TINKERPOP3-781
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-781
> Project: TinkerPop 3
> Issue Type: Improvement
> Reporter: Matt Frantz
>
> Currently, if we do an aggregating step (e.g. {{fold}}, {{groupCount}}, etc.)
> within the {{local}} step, we lose the path information.
> {noformat}
> gremlin> g.V(1).local(both().fold()).path()
> ==>[[v[3], v[2], v[4]]]
> {noformat}
> It would be better if the preceding portion of the path were still retained
> like so:
> {noformat}
> gremlin> g.V(1).local(both().fold()).path()
> ==>[v[1], [v[3], v[2], v[4]]]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
