[
https://issues.apache.org/jira/browse/TINKERPOP3-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15025294#comment-15025294
]
Marko A. Rodriguez commented on TINKERPOP3-958:
-----------------------------------------------
You know what else we could do for {{profileWithResults()}}.
{code}
gremlin> g.V.out.profileWithResults()
==>Traversal Metrics
===========================
BlahStep
BlooStep
==>v[1]
==>v[2]
==>v[3]
{code}
Thus, you get a {{Traversal<Vertex,Object>}}. The first answer is the
{{TraversalMetric}}. The rest is the query results....
> Improve usability of .profile() step.
> -------------------------------------
>
> Key: TINKERPOP3-958
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-958
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: process
> Reporter: Bob Briody
> Assignee: Marko A. Rodriguez
> Fix For: 3.1.1-incubating
>
>
> The .profile() step is currently tedious to use. One must remember this
> entire string to activate profiling and cap off the result:
> "profile().cap(TraversalMetrics.METRICS_KEY)".
> This should be streamlined.
> Additionally, if the TraversalMetrics are cap'd off the end of the traversal
> then this step and the duration it takes should be excluded from the metrics
> and timers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
