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.
Imported from Jira BEAM-237. Original Jira may contain additional context.
Reported by: mshields822.
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.
Imported from Jira BEAM-237. Original Jira may contain additional context.
Reported by: mshields822.