[
https://issues.apache.org/jira/browse/FLINK-14570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16963720#comment-16963720
]
vinoyang commented on FLINK-14570:
----------------------------------
[~sjwiesman] Re-understand your comments and feel that the design here has a
problem. We opened the {{TimerService}} service, but in the
{{KeyedStateBootstrapOperator}} we reused the {{SimpleTimerService}}. If we
don't expect the Timer to be fired. Then a better design is:
* Reimplement the {{TimerService}} and throw an exception in
registerXXXTimeTimer, or;
* Only partially open the {{TimeService}} in the
{{KeyedStateBootstrapFunction.Context}};
cc [~aljoscha] WDYT?
> KeyedStateBootstrapFunction missed onTimer callback method to fire timer
> ------------------------------------------------------------------------
>
> Key: FLINK-14570
> URL: https://issues.apache.org/jira/browse/FLINK-14570
> Project: Flink
> Issue Type: New Feature
> Components: API / State Processor
> Reporter: vinoyang
> Priority: Major
>
> In {{KeyedStateBootstrapFunction#Context}} we provided a {{TimerService}}
> which can be used to querying time and register timer. However, we may not be
> able to fire the timer.
> IMO, we'd better provide a {{onTimer}} callback method(just like
> {{KeyedProcessFunction}}) to expose this feature.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
