[
https://issues.apache.org/jira/browse/FLINK-20491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246537#comment-17246537
]
Dawid Wysakowicz commented on FLINK-20491:
------------------------------------------
For the first part I agree, lets see how easy it is to implement that.
As for the {{BatchExecutionKeyedStateBackend}} some food for thought. We could
try and return the "current key" in the two methods, not sure how easy would it
be to access the namespaces though, as they are not directly exposed in the
{{BatchExecutionKeyedStateBackend}}, but rather in each {{*State}} separately.
> Support Broadcast State in BATCH execution mode
> -----------------------------------------------
>
> Key: FLINK-20491
> URL: https://issues.apache.org/jira/browse/FLINK-20491
> Project: Flink
> Issue Type: Improvement
> Components: API / DataStream
> Reporter: Aljoscha Krettek
> Assignee: Aljoscha Krettek
> Priority: Major
> Labels: pull-request-available
>
> Right now, we don't support {{DataStream.connect(BroadcastStream)}} in
> {{BATCH}} execution mode. I believe we can add support for this with not too
> much work.
> The key insight is that we can process the broadcast side before the
> non-broadcast side. Initially, we were shying away from this because of
> concerns about {{ctx.applyToKeyedState()}} which allows the broadcast side of
> the user function to access/iterate over state from the keyed side. We
> thought that we couldn't support this. However, since we know that we process
> the broadcast side first we know that the keyed side will always be empty
> when doing so. We can thus just make this "keyed iteration" call a no-op,
> instead of throwing an exception as we do now.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
