[
https://issues.apache.org/jira/browse/FLINK-8667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16378642#comment-16378642
]
ASF GitHub Bot commented on FLINK-8667:
---------------------------------------
Github user kl0u commented on the issue:
https://github.com/apache/flink/pull/5500
The reason is what @tillrohrmann described. That also the other contexts do
not have access to the key either. This is **partially** a design reason (for
security), as we do not create defensive copies for performance reasons and if
the user code modifies the key, then we may have issues, and **partially**
something that we did not consider so important to expose in the beginning.
> expose key in KeyedBroadcastProcessFunction#onTimer()
> -----------------------------------------------------
>
> Key: FLINK-8667
> URL: https://issues.apache.org/jira/browse/FLINK-8667
> Project: Flink
> Issue Type: Improvement
> Affects Versions: 1.5.0
> Reporter: Bowen Li
> Assignee: Bowen Li
> Priority: Major
> Fix For: 1.5.0
>
>
> [~aljoscha] [~pnowojski]
> Since KeyedBroadcastProcessFunction is about to get out of the door, I think
> it will be great to expose the timer's key in KeyedBroadcastProcessFunction
> too. If we don't do it now, it will be much more difficult to add the feature
> on later because of user app compatibility issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
