Hi, the reasoning behind the limited user facing API was that we were (are) not sure whether we would be able to support efficient deletion of timers for different ways of storing timers.
@Stephan, If I remember correctly you were the strongest advocate for not allowing timer deletion. What’s your thinking on this? There was also a quick discussion on https://issues.apache.org/jira/browse/FLINK-3089 <https://issues.apache.org/jira/browse/FLINK-3089> where Xiaogang explained that the (new, not merged) RocksDB based timers would have efficient timer deletion. Best, Aljoscha > On 20. Apr 2017, at 11:56, Jagadish Bihani <jagad...@helpshift.com> wrote: > > Hi > > I am working on a use case where I want to start a timer for a given event > type and when that timer expires it will perform certain action. This can be > done using Process Function. > > But I also want to cancel scheduled timer in case of some other types of > events. I also checked the implementation of HeapInternalTimerService which > implements InternalTimerService interface has those implementations already. > Also SimpleTimerService which overrides TimerService also uses > InternalTimerService and simply passes VoidNamespace.INSTANCE. > > So in a way we are using InternalTimerService interface's implementations > everywhere. > > So what is the reason that ProcessFunction.Context uses TimerService? Any > reason 'deleteEventTimeTimer' is not exposed to users? If I want to use the > deleteEvent functionality how should I go about it? > > -- > Thanks and Regards, > Jagadish Bihani
