beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Cwik (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (BEAM-2430) Java FnApiDoFnRunner to share across runners
Date Tue, 11 Jul 2017 22:27:00 GMT

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

Luke Cwik reopened BEAM-2430:
-----------------------------
      Assignee: Kenneth Knowles  (was: Luke Cwik)

PR/3432 was about writing a DoFnRunner for executing DoFns within the SDK harness and has
very little to do with creating a DoFnRunner that exercises the Fn API (registration, process
bundle, transmit data, ...) to tell an SDK harness to do some meaningful work over the Fn
API.

> 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: Kenneth Knowles
>              Labels: beam-python-everywhere
>             Fix For: 2.1.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
(v6.4.14#64029)

Mime
View raw message