beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Knowles (JIRA)" <>
Subject [jira] [Commented] (BEAM-2430) Java FnApiDoFnRunner to share across runners
Date Tue, 11 Jul 2017 23:03:00 GMT


Kenneth Knowles commented on BEAM-2430:

Ah, OK. From within the Java SDK harness, the DoFnRunner probably doesn't need to know about
the Fn API. So I got confused because the code in the PR called it a FnApiDoFnRunner. This
ticket is, indeed, for a FnApi\[Client\]DoFnRunner.

> Java FnApiDoFnRunner to share across runners
> --------------------------------------------
>                 Key: BEAM-2430
>                 URL:
>             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

View raw message