beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-2431) Model Runner interactions in RPC layer for Runner API
Date Fri, 04 Aug 2017 16:55:00 GMT


ASF GitHub Bot commented on BEAM-2431:

GitHub user tgroh opened a pull request:

    [BEAM-2431] Add GRPC to Compilation of the Runner API

    Follow this checklist to help us incorporate your contribution quickly and easily:
     - [ ] Make sure there is a [JIRA issue](
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
    Generates the JobService GRPC classes.

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

    $ git pull job_submission_api_java

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

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

    This closes #3687
commit 006db74b0b14f36a833840a16fdf68d37e79bb89
Author: Thomas Groh <>
Date:   2017-08-04T16:51:02Z

    Add GRPC to Compilation of the Runner API
    Generates the JobService GRPC classes.


> Model Runner interactions in RPC layer for Runner API
> -----------------------------------------------------
>                 Key: BEAM-2431
>                 URL:
>             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

View raw message