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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
