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/08/18 18:00:06 UTC

[jira] [Resolved] (BEAM-2431) Model Runner interactions in RPC layer for Runner API

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

Kenneth Knowles resolved BEAM-2431.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 2.2.0

> Model Runner interactions in RPC layer for Runner API
> -----------------------------------------------------
>
>                 Key: BEAM-2431
>                 URL: https://issues.apache.org/jira/browse/BEAM-2431
>             Project: Beam
>          Issue Type: New Feature
>          Components: beam-model-runner-api
>            Reporter: Kenneth Knowles
>            Assignee: Sourabh Bajaj
>              Labels: beam-python-everywhere
>             Fix For: 2.2.0
>
>
> The "Runner API" today is actually just a definition of what constitutes a Beam pipeline. It needs to actually be a (very small) API.
> This would allow e.g. a Java-based job launcher to respond to launch requests and state queries from a Python-based adapter.
> The expected API would be something like a distillation of the APIs for PipelineRunner and PipelineResult (which is really "Job") via analyzing how these both look in Java and Python.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)