reuvenlax commented on pull request #15123: URL: https://github.com/apache/beam/pull/15123#issuecomment-889437010
Correct - this is a long-standing bug that has bitten a number of users. State variables are updated immediately, but timer state only updated between bundles. This meant that if you tried to keep the timer timestamps in state, you would sometimes observe inconsistent results depending on how the runner bundled things. The recent addition of Timer.clear() makes this even worse, as you could clear a timer and then have it still fire if it was already in the bundle. On Thu, Jul 29, 2021 at 1:25 PM Steven Niemitz ***@***.***> wrote: > it seems like the intent here is to make it so timers set/cleared in a > bundle can modify timers that were queued to fire in the same bundle (so > they no longer fire)? Am I understanding the problem correctly? > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/apache/beam/pull/15123#issuecomment-889434662>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AFAYJVPM23MP3OHPJBITKRTT2G2NLANCNFSM47XSKCSA> > . > -- 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]
