[GitHub] [beam] kennknowles commented on issue #23129: [Bug]: Issues with Watermark propagation in Spark runner (streaming)

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

kennknowles commented on issue #23129:
URL: https://github.com/apache/beam/issues/23129#issuecomment-1245939211

   Hmm, seems like a major problem. There really must be a watermark per PCollection. In fact, to do timers right you need
   
   1. watermark for incoming elements (held by upstream and element timestamps, timers fire using this)
   2. watermark for incoming elements + queued timers (held also by timer output timestamps, GC fires using this)
   3. output watermark for each PCollection (related to the downstream watermarks but might not be equal if there is propagation queue)


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