[ 
https://issues.apache.org/jira/browse/FLINK-8322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16315038#comment-16315038
 ] 

ASF GitHub Bot commented on FLINK-8322:
---------------------------------------

Github user bowenli86 commented on the issue:

    https://github.com/apache/flink/pull/5236
  
    @aljoscha  @StephanEwen  This metadata of timers helps users to understand 
their timer usage and write logic in code to handle it.  I think it's really 
helpful and convenient to provide the data out-of-box. As you said, it can be 
expensive and can also be implemented as valuestate or something else by users. 
I'm fine to drop it


> 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)

Reply via email to