You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aljoscha Krettek (JIRA)" <ji...@apache.org> on 2017/10/24 09:42:00 UTC
[jira] [Commented] (FLINK-7900) Add a Rich KeySelector
[ https://issues.apache.org/jira/browse/FLINK-7900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16216616#comment-16216616 ]
Aljoscha Krettek commented on FLINK-7900:
-----------------------------------------
What is the extend of this issue? Or better, what does a {{RichKeySelector}} have access to? I'm asking because {{KeySelector}} is a very simple one-method interface right now, which makes it easy for StateBackends and other components to handle them. If they get a lifecycle and access to other components we lose that and I'm not sure who would be responsible for the lifecycle of a {{RichKeySelector}}.
> Add a Rich KeySelector
> ----------------------
>
> Key: FLINK-7900
> URL: https://issues.apache.org/jira/browse/FLINK-7900
> Project: Flink
> Issue Type: Improvement
> Components: DataStream API
> Reporter: Hai Zhou UTC+8
> Assignee: Hai Zhou UTC+8
> Priority: Critical
>
> Currently, we just have a `KeySelector` Function, maybe we should add a `RichKeySelector` RichFunction, for the user to read some configuration information to build the keySelector they need.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)