You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Dawid Wysakowicz (Jira)" <ji...@apache.org> on 2020/12/09 09:19:00 UTC

[jira] [Assigned] (FLINK-20491) Support Broadcast State in BATCH execution mode

     [ https://issues.apache.org/jira/browse/FLINK-20491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dawid Wysakowicz reassigned FLINK-20491:
----------------------------------------

    Assignee: Dawid Wysakowicz  (was: Aljoscha Krettek)

> 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: Dawid Wysakowicz
>            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)