Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-3659

Add ConnectWithBroadcast Operation

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.0.0
    • None
    • None
    • None

    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 because it will probably take a while until we add support for side-inputs in the API. This new operation would allow expressing new patterns that cannot be expressed with the currently expressed operations.

      This is the new proposed API (names are non-final):

      1) Add DataStream.connectWithBroadcast(DataStream) and KeyedStream.connectWithBroadcast(DataStream)
      2) Add ConnectedWithBroadcastStream, akin to ConnectedStreams/
      3) Add BroadcastFlatMap and TimelyBroadcastFlatMap as the user functions.

      Sketch of the user function:

      interface BroadcastFlatMapFunction {
        public void flatMap(IN in, Collector out);
        public void processBroadcastInput(BIN in);
      }
      

      The API names, function names are a bit verbose and we have to add two new different ones but I don't see a way around this with the current way the Flink API works.

      Attachments

        There are no Sub-Tasks for this issue.

        Activity

          People

            kkl0u Kostas Kloudas
            aljoscha Aljoscha Krettek
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: