You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/03/09 17:24:01 UTC

[jira] [Work logged] (BEAM-3803) Dataflow runner should handle metrics per the spec

     [ https://issues.apache.org/jira/browse/BEAM-3803?focusedWorklogId=78947&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-78947 ]

ASF GitHub Bot logged work on BEAM-3803:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 09/Mar/18 17:23
            Start Date: 09/Mar/18 17:23
    Worklog Time Spent: 10m 
      Work Description: apilloud commented on issue #4823: [BEAM-3803] [Nexmark] Handle both committed and attempted metrics
URL: https://github.com/apache/beam/pull/4823#issuecomment-371881267
 
 
   Looks like this can be rewritten entirely as a change within the dataflow runner.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 78947)
    Time Spent: 2h 50m  (was: 2h 40m)

> Dataflow runner should handle metrics per the spec
> --------------------------------------------------
>
>                 Key: BEAM-3803
>                 URL: https://issues.apache.org/jira/browse/BEAM-3803
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow
>            Reporter: Andrew Pilloud
>            Assignee: Andrew Pilloud
>            Priority: Major
>              Labels: nexmark
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> The dataflow runner only supports committed metrics for batch jobs and attempted metrics for streaming jobs. Nexmark should use the best available metric source.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)