[
https://issues.apache.org/jira/browse/BEAM-9945?focusedWorklogId=432821&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-432821
]
ASF GitHub Bot logged work on BEAM-9945:
----------------------------------------
Author: ASF GitHub Bot
Created on: 13/May/20 20:47
Start Date: 13/May/20 20:47
Worklog Time Spent: 10m
Work Description: ibzib merged pull request #11697:
URL: https://github.com/apache/beam/pull/11697
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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: 432821)
Time Spent: 0.5h (was: 20m)
> Use consistent element count for progress counter.
> --------------------------------------------------
>
> Key: BEAM-9945
> URL: https://issues.apache.org/jira/browse/BEAM-9945
> Project: Beam
> Issue Type: Improvement
> Components: beam-model, sdk-go, sdk-java-harness, sdk-py-harness
> Reporter: Robert Bradshaw
> Assignee: Robert Bradshaw
> Priority: Critical
> Fix For: 2.21.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This influences how the SDK communicates progress and how splitting is
> performed.
> We currently inspect the element count of the output (which has inconsistent
> definitions across SDKs, see BEAM-9934). Instead, we can move to using an
> explicit, separate metric.
> This can currently lead to incorrect progress reporting and in some cases
> even a crash in the UW depending on the SDK, and makes it more difficult (but
> not impossible) to fix element counts in the future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
