You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/06/03 15:06:28 UTC
[GitHub] [beam] damccorm opened a new issue, #17839: Merging of watermark holds depends on runner-specific "take the minimum" behavior
damccorm opened a new issue, #17839:
URL: https://github.com/apache/beam/issues/17839
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](https://issues.apache.org/jira/browse/BEAM-24). Original Jira may contain additional context.
Reported by: kenn.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [beam] damccorm closed issue #17839: Merging of watermark holds depends on runner-specific "take the minimum" behavior
Posted by GitBox <gi...@apache.org>.
damccorm closed issue #17839: Merging of watermark holds depends on runner-specific "take the minimum" behavior
URL: https://github.com/apache/beam/issues/17839
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@beam.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org