When multiple watermark holds are to be combined via an OutputTimeFn and committed to persistent storage, the case where the OutputTimeFn computes the minimum is elided, assuming the underlying runner will perform this combine by default.
This is a natural default, but today it is a runner-specific behavior that the runner-agnostic code relies upon.
Imported from Jira BEAM-24. Original Jira may contain additional context.
Reported by: kenn.
When multiple watermark holds are to be combined via an OutputTimeFn and committed to persistent storage, the case where the OutputTimeFn computes the minimum is elided, assuming the underlying runner will perform this combine by default.
This is a natural default, but today it is a runner-specific behavior that the runner-agnostic code relies upon.
Imported from Jira BEAM-24. Original Jira may contain additional context.
Reported by: kenn.