[ 
https://issues.apache.org/jira/browse/FLINK-8667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16378819#comment-16378819
 ] 

ASF GitHub Bot commented on FLINK-8667:
---------------------------------------

Github user pnowojski commented on the issue:

    https://github.com/apache/flink/pull/5500
  
    If this security concern is an issue, maybe in that case `getCurrentKey()` 
should take `object-reuse` into account, and if `object-reuse` is set to false, 
make a defensive copy of the key on access?
    
    However @aljoscha was not objecting the general idea in the other PR: 
https://github.com/apache/flink/pull/5481


> 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)

Reply via email to