[
https://issues.apache.org/jira/browse/TINKERPOP-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167960#comment-15167960
]
ASF GitHub Bot commented on TINKERPOP-958:
------------------------------------------
Github user rjbriody commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/242#issuecomment-189005146
Nope.
These are the 2 things possible before:
```
t = g.V().profile()
t.iterate()
metrics =
t.asAdmin().getSideEffects().get(TraversalMetrics.METRICS_KEY).get()
```
or
```
g.V().profile().cap(TraversalMetrics.METRICS_KEY)
```
Neither of which behave the same way now.
> Improve usability of .profile() step.
> -------------------------------------
>
> Key: TINKERPOP-958
> URL: https://issues.apache.org/jira/browse/TINKERPOP-958
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Reporter: Bob Briody
> Assignee: Marko A. Rodriguez
> Fix For: 3.2.0-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.- (Moved to own ticket:
> https://issues.apache.org/jira/browse/TINKERPOP-1078)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
