[
https://issues.apache.org/jira/browse/TINKERPOP3-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14520547#comment-14520547
]
Matthias Broecheler commented on TINKERPOP3-651:
------------------------------------------------
The other thing you need to look into is how a vendor gets access to the
metrics. It seems that allMetrics is indexed by the profileStepId to which the
vendor doesn't really have access (unless you do some cumbersome navigation on
the traversal) - why not index by the stepId?
> TraversalMetrics framework is not sufficient for vendor extension
> -----------------------------------------------------------------
>
> Key: TINKERPOP3-651
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-651
> Project: TinkerPop 3
> Issue Type: Bug
> Components: process
> Affects Versions: 3.0.0.GA
> Reporter: Bob Briody
> Priority: Minor
>
> The StandardTraversalMetrics class must provide the necessary getters to
> enable a vendor to augment the Metrics data.
> As of right now the API is missing a way for vendors to obtain the actual
> (not computed) metrics.
> In order to ensure there are no other omissions, there should be a test case
> that mocks a vendor's behavior and augments the TraversalMetrics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
