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 2020/08/13 13:29:49 UTC

[GitHub] [beam] mxm edited a comment on pull request #12551: [DISCUSS] [BEAM-10691] keep track of timers creating watermark hold

mxm edited a comment on pull request #12551:
URL: https://github.com/apache/beam/pull/12551#issuecomment-673478937


   I'm not following. How's adding a unnecessarily restrictive assertion a proof that there is a bug? At any point in time there can be multiple timers which set an output timestamp hold on the same timestamp. Please keep in mind that multiple keys can set set a single timer with a different output timestamp. That does not indicate a bug. 
   
   The priority queue is a global view over all keys. The watermark will not be advanced past`t` if for any key there exists a timer with the output timestamp `t`.


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

For queries about this service, please contact Infrastructure at:
users@infra.apache.org