[
https://issues.apache.org/jira/browse/BEAM-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17145665#comment-17145665
]
Beam JIRA Bot commented on BEAM-237:
------------------------------------
This issue was marked "stale-P2" and has not received a public comment in 14
days. It is now automatically moved to P3. If you are still affected by it, you
can comment and move it back to P2.
> 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.3.4#803005)
