Can you explain the use case? You can already overwrite a timer with a new
time. Do you have a specific use case where you want to delete, not
overwrite, a timer?
I don't think this would be terribly hard to implement, but I'm curious
about the use case.
Reuven
On Tue, Jan 7, 2020 at 8:11 PM Rez
The model already requires functionality for deleting timers. If a timer
is set more than once, the last invocation must override all the other.
In Flink deleting timers is as expensive as setting them.
-Max
On 08.01.20 05:10, Reza Rokni wrote:
Hi,
Was exploring the ability to add unset / re
Hi,
Was exploring the ability to add unset / reset option for Timer, would this
be an expensive operation for runners to support?
More complex State and Timer use cases can require this operation and while
its possible to do today using a separate State Object, its heavy on boiler
plate and cumbe
