mxm edited a comment on pull request #12551: URL: https://github.com/apache/beam/pull/12551#issuecomment-673621651
Yes, that timer map utilizes Flink's keyed state backend which always takes the currently active key into account. The map is necessary for allowing to cancel the currently active timer if we set a new timer for that key. Flink doesn't support that out of the box without you knowing the previous timestamp the timer was set to. I added that note because somebody tried to use this map for calculating the hold which does not work. You can iterate over all keys (we do that during restore) but that is a very expensive operation you don't want to perform per-element. ---------------------------------------------------------------- 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: [email protected]
