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

Aljoscha Krettek updated FLINK-3659:
------------------------------------
    Description: 
We should add a new operation that has a main input that can be keyed (but 
doesn't have to be) and a second input that is always broadcast. This is 
similar to a {{CoFlatMap}} or {{CoMap}} but there either both inputs have to be 
keyed or non-keyed.

This builds on FLINK-4940 which aims at adding broadcast/global state. When 
processing an element from the broadcast input only access to broadcast state 
is allowed. When processing an element from the main input access both the 
regular keyed state and the broadcast state can be accessed.

I'm proposing this as an intermediate/low-level operation This new operation 
would allow expressing new patterns that cannot be expressed with the currently 
expressed operations.

  was:
We should add a new operation that has a main input that can be keyed (but 
doesn't have to be) and a second input that is always broadcast. This is 
similar to a {{CoFlatMap}} or {{CoMap}} but there either both inputs have to be 
keyed or non-keyed.

This builds on 
This new operation would allow expressing new patterns that cannot be expressed 
with the currently expressed operations.


> Add ConnectWithBroadcast Operation
> ----------------------------------
>
>                 Key: FLINK-3659
>                 URL: https://issues.apache.org/jira/browse/FLINK-3659
>             Project: Flink
>          Issue Type: Improvement
>          Components: Streaming
>    Affects Versions: 1.0.0
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
>
> We should add a new operation that has a main input that can be keyed (but 
> doesn't have to be) and a second input that is always broadcast. This is 
> similar to a {{CoFlatMap}} or {{CoMap}} but there either both inputs have to 
> be keyed or non-keyed.
> This builds on FLINK-4940 which aims at adding broadcast/global state. When 
> processing an element from the broadcast input only access to broadcast state 
> is allowed. When processing an element from the main input access both the 
> regular keyed state and the broadcast state can be accessed.
> I'm proposing this as an intermediate/low-level operation This new operation 
> would allow expressing new patterns that cannot be expressed with the 
> currently expressed operations.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to