Mailing-List: contact commits-help@beam.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@beam.apache.org
Date: Tue, 11 Jul 2017 21:44:00 +0000 (UTC)
From: "Kenneth Knowles (JIRA)" <jira@apache.org>
To: commits@beam.apache.org
Message-ID: <JIRA.13078712.1497033175000.222305.1499809440209@Atlassian.JIRA>
In-Reply-To: <JIRA.13078712.1497033175000@Atlassian.JIRA>
References: <JIRA.13078712.1497033175000@Atlassian.JIRA> <JIRA.13078712.1497033175435@jira-lw-us.apache.org>
Subject: [jira] [Resolved] (BEAM-2430) Java FnApiDoFnRunner to share across
 runners
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 11 Jul 2017 21:44:05 -0000


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

Kenneth Knowles resolved BEAM-2430.
-----------------------------------
       Resolution: Implemented
    Fix Version/s: 2.1.0

> 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: Luke Cwik
>              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)