You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Bob Briody (JIRA)" <ji...@apache.org> on 2015/04/02 18:55:52 UTC
[jira] [Resolved] (TINKERPOP3-117) Traversal .explain()
[ https://issues.apache.org/jira/browse/TINKERPOP3-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bob Briody resolved TINKERPOP3-117.
-----------------------------------
Resolution: Fixed
done
> Traversal .explain()
> --------------------
>
> Key: TINKERPOP3-117
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-117
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: process
> Reporter: Bob Briody
>
> Add .explain() functionality to Traversal.
> .explain() would provide details about the execution plan of the Traversal that can be known before it is executed.
> .explain() would show the optimized Traversal (similar to .toString() output).
> For each (post optimization) step:
> - Does this step utilize an index?
> - Will this step scan all vertices or edges in the graph?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)