[
https://issues.apache.org/jira/browse/FLINK-20491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17247268#comment-17247268
]
Aljoscha Krettek commented on FLINK-20491:
------------------------------------------
I extended my work-in-progress PR: https://github.com/apache/flink/pull/14312
For the wiring, I'm extending {{StreamConfig.InputConfig}} to allow specifying
a requirement of {{SORTED}} or {{PASS_THROUGH}}. With this, I'm removing the
"global" {{SORTED_INPUTS}} field of {{StreamConfig}} because we now allow more
fine-grained control.
I still have to clean up the commits and add more Javadocs, but WDYT so far?
> 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)
