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/04 14:34:27 UTC

[GitHub] [beam] damccorm opened a new issue, #19957: Dataflow streaming timers are not strictly time ordered when set earlier mid-bundle

damccorm opened a new issue, #19957:
URL: https://github.com/apache/beam/issues/19957

   Let's suppose we have the following situation:
    - statful ParDo with two timers - timerA and timerB
    - timerA is set for window.maxTimestamp() **** 1
    - timerB is set anywhere between <windowStart, windowEnd), let's denote that timerB.timestamp
    - input watermark moves to BoundedWindow.TIMESTAMP_MAX_VALUE
   
   Then the order of timers is as follows (correct):
    - timerB
    - timerA
   
   But, if timerB sets another timer (say for timerB.timestamp **** 1), then the order of timers will be:
    - timerB (timerB.timestamp)
    - timerA (BoundedWindow.TIMESTAMP_MAX_VALUE)
    - timerB (timerB.timestamp **** 1)
   
   Which is not ordered by timestamp. The reason for this is that when the input watermark update is evaluated, the WatermarkManager,extractFiredTimers() will produce both timerA and timerB. That would be correct, but when timerB sets another timer, that breaks this.
   
   
   Imported from Jira [BEAM-8543](https://issues.apache.org/jira/browse/BEAM-8543). Original Jira may contain additional context.
   Reported by: janl.


-- 
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] lukecwik closed issue #19957: Dataflow streaming timers are not strictly time ordered when set earlier mid-bundle

Posted by GitBox <gi...@apache.org>.
lukecwik closed issue #19957: Dataflow streaming timers are not strictly time ordered when set earlier mid-bundle
URL: https://github.com/apache/beam/issues/19957


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