You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Kenneth Knowles (JIRA)" <ji...@apache.org> on 2017/10/27 04:48:01 UTC
[jira] [Assigned] (BEAM-2430) Java FnApiDoFnRunner to share across
runners
[ https://issues.apache.org/jira/browse/BEAM-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kenneth Knowles reassigned BEAM-2430:
-------------------------------------
Assignee: Thomas Groh (was: Kenneth Knowles)
> 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
> Labels: portability
>
> 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
(v6.4.14#64029)