[GitHub] [beam] iht commented on issue #23379: [Feature Request]: Expose TimerStateInternals.currentOutputWatermarkTime to allow for DoFns to handle elements behind the watemark differently

[GitBox <gi...@apache.org>]

iht commented on issue #23379:
URL: https://github.com/apache/beam/issues/23379#issuecomment-1260578847

   In my experience, this is a need demanded by several users of Beam. For instance, in the Beam book written by @je-ik, there are a couple of examples of how to achieve something similar by filtering out some messages before a window is applied ([example 1](https://github.com/PacktPublishing/Building-Big-Data-Pipelines-with-Apache-Beam/blob/main/chapter3/src/main/java/com/packtpub/beam/chapter3/DroppableDataFilter.java), [example 2](https://github.com/PacktPublishing/Building-Big-Data-Pipelines-with-Apache-Beam/blob/main/chapter3/src/main/java/com/packtpub/beam/chapter3/DroppableDataFilter2.java)). The implementation of those examples would be straightforward if the process context would expose the value of the watermark.


-- 
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