[
https://issues.apache.org/jira/browse/BEAM-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132171#comment-17132171
]
Beam JIRA Bot commented on BEAM-237:
------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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)
