[ 
https://issues.apache.org/jira/browse/TINKERPOP-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089488#comment-15089488
 ] 

ASF GitHub Bot commented on TINKERPOP-1078:
-------------------------------------------

GitHub user rjbriody opened a pull request:

    https://github.com/apache/incubator-tinkerpop/pull/194

    Tinkerpop 1078: Do not include TraversalMetrics cap in profile results.

    https://issues.apache.org/jira/browse/TINKERPOP-1078
    
    If the last step in a Traversal that is being profiled is 
```cap(TraversalMetrics.METRICS_KEY)``` then that step is not profiled and not 
included as a row in the TraversalMetrics results.
    
    Includes tests.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/rjbriody/incubator-tinkerpop TINKERPOP-1078

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-tinkerpop/pull/194.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #194
    
----
commit 208910695b3b37bfc7a80c3cdfe945c931edf2c5
Author: rjbriody <bob.bri...@datastax.com>
Date:   2016-01-07T20:52:19Z

    Fix the way DependantMutableMetrics profiler durations are calculated.

commit d88de29e0a0c372419279b049c128c613c10c361
Author: rjbriody <bob.bri...@datastax.com>
Date:   2016-01-08T16:48:45Z

    Do not include TraversalMetrics cap in profile results.

----


> Do not include TraversalMetrics cap in profile results.
> -------------------------------------------------------
>
>                 Key: TINKERPOP-1078
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1078
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.1.1-incubating
>            Reporter: Bob Briody
>             Fix For: 3.1.1-incubating
>
>
> _As a user profiling a traversal, I am likely to cap the TraversalMetrics 
> results, but I don't actually want that Step included in my profile._
> When the TraversalMetrics are cap'd off the end of the traversal the .cap() 
> Step should be excluded from the metrics and timers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to