[
https://issues.apache.org/jira/browse/FLINK-8322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16315408#comment-16315408
]
ASF GitHub Bot commented on FLINK-8322:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/5236
If we want to implement something like that, we should tap into what the
data structures give us anyways, so we don't add additional overhead. Its a bit
tricky to do that, though, because especially for RocksDB, it is not easily
possible to know the number of keys at any point in time (due to the LSM model
and the lazy merging).
> support getting number of existing timers in TimerService
> ---------------------------------------------------------
>
> Key: FLINK-8322
> URL: https://issues.apache.org/jira/browse/FLINK-8322
> Project: Flink
> Issue Type: Improvement
> Components: DataStream API
> Affects Versions: 1.4.0
> Reporter: Bowen Li
> Assignee: Bowen Li
> Fix For: 1.5.0
>
>
> There are pretty common use cases where users want to use timers as scheduled
> threads - e.g. add a timer to wake up x hours later and do something (reap
> old data usually) only if there's no existing timers, basically we only want
> at most 1 timer exists for the key all the time
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
