[
https://issues.apache.org/jira/browse/BEAM-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Groh resolved BEAM-2430.
-------------------------------
Resolution: Done
Fix Version/s: 2.3.0
I claim that a {{FnApiDoFnRunner}} is the wrong abstraction. However, a similar
concept exists in the SdkHarnessClient, BundleProcessor, and ActiveBundle
abstractions introduced in [https://github.com/apache/beam/pull/4472,] which is
what clients who wish to use the portability framework should use when sending
data to a remote Sdk Harness.
> Java FnApiDoFnRunner to share across runners
> --------------------------------------------
>
> Key: BEAM-2430
> URL: https://issues.apache.org/jira/browse/BEAM-2430
> Project: Beam
> Issue Type: New Feature
> Components: runner-core
> Reporter: Kenneth Knowles
> Assignee: Thomas Groh
> Priority: Major
> Labels: portability
> Fix For: 2.3.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
