[
https://issues.apache.org/jira/browse/FLINK-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630678#comment-15630678
]
Gyula Fora commented on FLINK-4992:
-----------------------------------
Well, it doesn't have to be Strings but there should be a way of attaching some
sort of metadata to the registered timer (like the namespace internally). Can
you please explain what you meant by different timer services? Do you mean
attaching metadata to the timerservice instead of the actual registered timer?
> Expose String parameter for timers in Timely functions and TimerService
> -----------------------------------------------------------------------
>
> Key: FLINK-4992
> URL: https://issues.apache.org/jira/browse/FLINK-4992
> Project: Flink
> Issue Type: Improvement
> Components: Streaming
> Affects Versions: 1.2.0
> Reporter: Gyula Fora
> Priority: Minor
>
> Currently it is very hard to register and execute multiple different types
> timers from the same user function because timers don't carry any metadata.
> We propose to extend the timer registration and onTimer logic by attaching a
> String argument so users of these features can implement functionality that
> depends on this addtitional metadata.
> The proposed new methods:
> In the TimerService:
> void registerProcessingTimeTimer(long time, String label);
> void registerEventTimeTimer(long time, String label);
> In the TimelyFunctions:
> void onTimer(long timestamp, String label, TimeDomain timeDomain,
> TimerService timerService...);
> This extended functionality can be mapped to a String namespace for the
> internal timer service. I suggest we don't use the term "namespace" here
> because it just complicates things for the users, I think "label" or "id" or
> "name" is much simpler to understand.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
