[
https://issues.apache.org/jira/browse/BEAM-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132610#comment-17132610
]
Kenneth Knowles commented on BEAM-237:
--------------------------------------
Similar in spirit to https://s.apache.org/beam-sink-triggers. This would be a
massive new features for Beam, potentially needing implementation now and
becoming default in Beam 3.0
> Should use allowedLateness from downstream computations in ReduceFnRunner
> --------------------------------------------------------------------------
>
> Key: BEAM-237
> URL: https://issues.apache.org/jira/browse/BEAM-237
> Project: Beam
> Issue Type: Bug
> Components: runner-core
> Reporter: Mark Shields
> Priority: P2
> Labels: stale-P2
>
> 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)
