[jira] [Comment Edited] (BEAM-237) Should use allowedLateness from downstream computations in ReduceFnRunner

["Danny McCormick (Jira)" <ji...@apache.org>]

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

Danny McCormick edited comment on BEAM-237 at 6/3/22 3:38 PM:
--------------------------------------------------------------

This issue has been migrated to [https://github.com/apache/beam/issues/17864]


was (Author: JIRAUSER282469):
This isn't actually real, but this issue has been migrated to https://github.com/apache/beam/issues/17864

> Should use allowedLateness from downstream computations in ReduceFnRunner 
> --------------------------------------------------------------------------
>
>                 Key: BEAM-237
>                 URL: https://issues.apache.org/jira/browse/BEAM-237
>             Project: Beam
>          Issue Type: Wish
>          Components: runner-core
>            Reporter: Mark Shields
>            Priority: P3
>
> Much of the reasoning about holds, late data and final panes in ReduceFnRunner assume the current getAllowedLateness is an upper bound of the getAllowedLateness of all downstream computations.
> There is currently no test that this is indeed the case.
> It may be much simpler (for us and our users) to have a global allowed lateness setting.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)