[ https://issues.apache.org/jira/browse/FLINK-9529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-9529: ---------------------------------- Labels: auto-unassigned (was: stale-assigned) > Do not expose keyed operations on ProcessFunction.Context > --------------------------------------------------------- > > Key: FLINK-9529 > URL: https://issues.apache.org/jira/browse/FLINK-9529 > Project: Flink > Issue Type: Sub-task > Components: API / DataStream > Affects Versions: 1.5.0 > Reporter: Till Rohrmann > Priority: Major > Labels: auto-unassigned > > Currently, the {{ProcessFunction}} provides a {{Context}} object from which > on can access the {{TimerService}}. The {{TimerService}} allows to register > timers if one operates on a keyed stream. If it is not a keyed stream, then > this operation fails. Recently, we added a {{KeyedProcessFunction}} which > captures this semantic difference. I would propose to clean up the > {{Context}} interface to give only access to supported operations when > operating on a non-keyed and keyed state respectively. -- This message was sent by Atlassian Jira (v8.3.4#803005)