Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-2430

Java FnApiDoFnRunner to share across runners

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Resolved
    • P2
    • Resolution: Done
    • None
    • 2.3.0
    • runner-core

    Description

      As the portability framework comes into focus, let's fill out the support code for making it easy to onboard a new runner.

      There is some amount of using the Fn API that has to do only with the fact that a runner is implemented in Java, and is not specific to that runner. This should be part of the runners-core library, and designed so that a runner can set it up however it likes, and just pass elements without having to explicitly manage things like requests, responses, protos, and coders.

      Attachments

        Issue Links

          is depended upon by

          Sub-task - The sub-task of the issue BEAM-2598 SparkRunner Fn API based ParDo operator

          • P2 - Default priority. Will be triaged and planned according to community practices.
          • Resolved

          Sub-task - The sub-task of the issue BEAM-2599 ApexRunner Fn API based ParDo operator

          • P2 - Default priority. Will be triaged and planned according to community practices.
          • Resolved
          links to

          Web Link Github Pull Request #3432

          Web Link GitHub Pull Request #3750

          Activity

            People

              tgroh Thomas Groh
              kenn Kenneth Knowles
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: