shunping commented on issue #35176: URL: https://github.com/apache/beam/issues/35176#issuecomment-2949300169
> Clear is a convenience action for when the user code knows the timers shouldn't run based on state they've stored. That state is independent of whether the timer executed or not. I agree. That's also what I have in my first example: the clear action is called when the count (a state) reaches 3. Anyway, the workaround I proposed (by adding the LAST_TIMESTAMP state) seems to work on different bundle sizes: the clear action is only called when it is going to clear a timer in the future ET. Maybe this is too specific to my use case though. With all that said, I still think that if a timer behavior is relying on bundle size, it is a problem. It will be great if we can clearly say this is a "yes" or "no", rather than a "maybe"... -- 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]
