You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Mark Shields (JIRA)" <ji...@apache.org> on 2016/04/28 20:20:12 UTC
[jira] [Updated] (BEAM-237) Should use allowedLateness from
downstream computations in ReduceFnRunner
[ https://issues.apache.org/jira/browse/BEAM-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Shields updated BEAM-237:
------------------------------
Description:
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.
was:
Much of the reasoning about holds, late data and final panes in ReduceFnRunner assuming 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.
> 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
> Assignee: Frances Perry
>
> 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
(v6.3.4#6332)