lostluck commented on issue #35176:
URL: https://github.com/apache/beam/issues/35176#issuecomment-2948288959
* yes, this seems correct.
* This is only defined if the runner promises event time ordering of
elements per key, which isn't guaranteed across all transforms in the model.
As a separate point, is it reasonable for a data element to clear a timer if
the timer Callback code is assuming it runs?
Timers self clear when they run, so why manually clear it? It's situational.
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.
We can't always assume we know better than the user code being executed.
Recall that the user code can't know or assume anything about the bundle size
either. To do so is a programing error.
--
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]
