[jira] [Updated] (FLINK-4992) Expose String parameter for timers in Timely functions and TimerService

["Konstantin Knauf (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Knauf updated FLINK-4992:
------------------------------------
      Labels:   (was: auto-closed)
    Priority: Not a Priority  (was: Minor)

> 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: API / DataStream
>    Affects Versions: 1.2.0
>            Reporter: Gyula Fora
>            Priority: Not a Priority
>
> 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
(v8.3.4#803005)