You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "boshu Zheng (JIRA)" <ji...@apache.org> on 2018/12/13 03:21:00 UTC

[jira] [Assigned] (FLINK-9529) Do not expose keyed operations on ProcessFunction.Context

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

boshu Zheng reassigned FLINK-9529:
----------------------------------

    Assignee: boshu Zheng

> 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: Java API
>    Affects Versions: 1.5.0
>            Reporter: Till Rohrmann
>            Assignee: boshu Zheng
>            Priority: Major
>
> 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
(v7.6.3#76005)