You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2017/02/15 00:44:43 UTC

[jira] [Updated] (TINKERPOP-969) respawn

     [ https://issues.apache.org/jira/browse/TINKERPOP-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stephen mallette updated TINKERPOP-969:
---------------------------------------
    Fix Version/s:     (was: 3.2.4)
                   3.2.5

> respawn
> -------
>
>                 Key: TINKERPOP-969
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-969
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.0.2-incubating
>            Reporter: Matt Frantz
>            Assignee: Marko A. Rodriguez
>             Fix For: 3.2.5
>
>
> Control which aspects of the traverser propagate into an inner traversal by using the {{respawn}} factory method.
> {noformat}
> // Clone only the location by default.
> g.V.map(respawn().out('mother').name)
> // Clone sack and path
> g.V.as('a').map(
>   respawn(sack,path).
>   sack().as('s').select('a','s'))
> {noformat}
> We would also like to allow the inner traversal to have its own sack and side-effect scope.  This would require something that returns a {{GraphTraversalSource}}, e.g. {{respawnSource}}.  That also means that {{GraphTraversalSource}} needs a new step, e.g. {{identity}}, that would allow it to be used as an inner traversal.
> {noformat}
> // can have its own sack definition
> g.V.map(respawnSource().withSack(0.0).identity().out()...)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)