[
https://issues.apache.org/jira/browse/FLINK-8560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16360156#comment-16360156
]
Bowen Li commented on FLINK-8560:
---------------------------------
[~aljoscha] [~pnowojski] I have taken a look at this, and am wondering if this
is worth it. If we take the approach that Piotr suggested, it means we need to
keep the key for every timer explicitly in memory, no matter users will use it
or not - is this worth the effort and memory overhead?
> Access to the current key in ProcessFunction after keyBy()
> ----------------------------------------------------------
>
> Key: FLINK-8560
> URL: https://issues.apache.org/jira/browse/FLINK-8560
> Project: Flink
> Issue Type: Wish
> Components: DataStream API
> Reporter: Jürgen Thomann
> Assignee: Bowen Li
> Priority: Minor
>
> Currently it is required to store the key of a keyBy() in the processElement
> method to have access to it in the OnTimerContext.
> This is not so good as you have to check in the processElement method for
> every element if the key is already stored and set it if it's not already set.
> A possible solution would adding OnTimerContext#getCurrentKey() or a similar
> method. Maybe having it in the open() method could maybe work as well.
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Getting-Key-from-keyBy-in-ProcessFunction-tt18126.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
