beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-2431) Model Runner interactions in RPC layer for Runner API
Date Mon, 31 Jul 2017 21:21:01 GMT

    [ https://issues.apache.org/jira/browse/BEAM-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107975#comment-16107975
] 

ASF GitHub Bot commented on BEAM-2431:
--------------------------------------

GitHub user sb2nov opened a pull request:

    https://github.com/apache/beam/pull/3667

    [BEAM-2431] Check in the job api and prototype of python direct runner

    This PR works with a test pipeline but we need some changes in the
    direct runner to get rid of the apply loop and split the run and
    execute function. But for an MVP version demonstrating the job api this
    should be good to go.
    
    R: @kennknowles PTAL
    
    Follow this checklist to help us incorporate your contribution quickly and easily:
    
     - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/projects/BEAM/issues/)
filed for the change (usually before you start working on it).  Trivial changes like typos
do not require a JIRA issue.  Your pull request should address just this issue, without pulling
in other changes.
     - [ ] Each commit in the pull request should have a meaningful subject line and body.
     - [ ] Format the pull request title like `[BEAM-XXX] Fixes bug in ApproximateQuantiles`,
where you replace `BEAM-XXX` with the appropriate JIRA issue.
     - [ ] Write a pull request description that is detailed enough to understand what the
pull request does, how, and why.
     - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will
be performed on your pull request automatically.
     - [ ] If this contribution is large, please file an Apache [Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf).
    
    ---


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sb2nov/beam BEAM-2431-beam-job-api

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/beam/pull/3667.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3667
    
----
commit 7845810a591e7f72493109b755e76bddaf03ee63
Author: Sourabh Bajaj <sourabhbajaj@google.com>
Date:   2017-07-31T21:19:30Z

    [BEAM-2431] Check in the job api and prototype of python direct runner
    
    This PR works with a test pipeline but we need some changes in the
    direct runner to get rid of the apply loop and split the run and
    execute function. But for an MVP version demonstrating the job api this
    should be good to go.

----


> 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
>
> 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)

Mime
View raw message