[
https://issues.apache.org/jira/browse/BEAM-3803?focusedWorklogId=78990&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-78990
]
ASF GitHub Bot logged work on BEAM-3803:
----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Mar/18 19:24
Start Date: 09/Mar/18 19:24
Worklog Time Spent: 10m
Work Description: kennknowles commented on issue #4841: BEAM-3803:
Dataflow runner implements metrics contract
URL: https://github.com/apache/beam/pull/4841#issuecomment-371919672
Strong agreement. If you have committed metrics, that number is clearly
within spec for attempted metrics (which can be pretty much any value at all,
when you get down to it).
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 78990)
Time Spent: 3h 20m (was: 3h 10m)
> 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: 3h 20m
> Remaining Estimate: 0h
>
> The dataflow runner only supports committed metrics for batch jobs and
> attempted metrics for streaming jobs. It should always support attempted
> metrics and throw an UnsupportedOperationException when the metrics are
> missing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
