[
https://issues.apache.org/jira/browse/FLINK-9152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16435817#comment-16435817
]
Aljoscha Krettek commented on FLINK-9152:
-----------------------------------------
Fixed on master in
584229dc00e62a6a8540b059645269bb04d0ba04
0838bbeaafed791d96bfd1e8e1f8a5e486c35325
48d05f12eac28a7f66dee68e0a0b0000ff557e26
f3d4011f80b3d6b25e55a354d1a41928074f02a0
> Harmonize BroadcastProcessFunction Context names
> ------------------------------------------------
>
> Key: FLINK-9152
> URL: https://issues.apache.org/jira/browse/FLINK-9152
> Project: Flink
> Issue Type: Improvement
> Components: DataStream API
> Affects Versions: 1.5.0
> Reporter: Aljoscha Krettek
> Assignee: Aljoscha Krettek
> Priority: Blocker
> Fix For: 1.5.0
>
>
> Currently, the {{Context}} on {{KeyedBroadcastProcessFunction}} is called
> {{KeyedContext}}, which is different from the name of the context on
> {{BroadcastProcessFunction}}. This leads to the strange combination of
> {code:java}
> public abstract void processBroadcastElement(final IN2 value, final
> KeyedContext ctx, final Collector<OUT> out) throws Exception;
> {code}
> i.e. you're processing a broadcast element but the context is called a
> "keyed" context.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
