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 2015/04/07 15:43:12 UTC

[jira] [Closed] (TINKERPOP3-585) Traversal.clone() Maintain State of Strategy Application

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

stephen mallette closed TINKERPOP3-585.
---------------------------------------
       Resolution: Duplicate
    Fix Version/s: 3.0.0.GA

this issue contains a subset of capability described in TINKERPOP-595 - closing in favor of that issue.

> Traversal.clone() Maintain State of Strategy Application
> --------------------------------------------------------
>
>                 Key: TINKERPOP3-585
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-585
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: process
>            Reporter: stephen mallette
>             Fix For: 3.0.0.GA
>
>
> When {{Traversal.clone()}} is called keep the state of the Traversal determining whether or not Traversal Strategies have been applied, and if applied, keep the clone to the state of the {{Traversal}} after their application.
> The purpose here is to make it so that a {{Traversal}} only needs to have its strategies applied once.  Such a capability could aid in performance by allowing a {{Traversal}} to be "prepared" ahead of time and re-used.
> I'm not familiar with the nature of {{clone}} and its current usage.  It may be that {{clone}} might be too low a level place to provide this functionality.  Perhaps other ways could be considered that don't touch the implementation of {{clone}}?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)