[
https://issues.apache.org/jira/browse/TINKERPOP3-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004174#comment-15004174
]
Bob Briody commented on TINKERPOP3-958:
---------------------------------------
I believe the common use-case is to want the TraversalMetrics to be the result
of the .profile() step. I do still think it is important to enable users to
obtain their regular traversal results and later access the TraversalMetrics as
can currently be done via the traversal's side effects post-iteration. However,
the common use case should be streamlined.
One possible, but not fantastic option, would be to have the profile step take
a parameter to describe it's behavior, and if not specified it would emit
TraversalMetrics. This could be a boolean parameter or possibly a more
descriptive constant.
> 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
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
