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-2899) Universal Local Runner
Date Mon, 09 Oct 2017 23:17:00 GMT


ASF GitHub Bot commented on BEAM-2899:

GitHub user tgroh opened a pull request:

    [BEAM-2899] Move the Job Server into a Submodule

    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
    This permits separation of the Job Server and the Java Runner which
    submits to it, while both being part of the 'ReferenceRunner'

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

    $ git pull reference_runner_module

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 #3967
commit ff8ff926c5c911c4bba78286aba2000439bda767
Author: Thomas Groh <>
Date:   2017-10-09T23:13:28Z

    Move the Job Server into a Submodule
    This permits separation of the Job Server and the Java Runner which
    submits to it, while both being part of the 'ReferenceRunner'


> Universal Local Runner
> ----------------------
>                 Key: BEAM-2899
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-core
>            Reporter: Henning Rohde
>            Assignee: Thomas Groh
>              Labels: portability
> To make the portability effort tractable, we should implement a Universal Local Runner
(ULR) in Java that runs in a single server process plus docker containers for the SDK harness
containers. It would serve multiple purposes:
>   (1) A reference implementation for other runners. Ideally, any new feature should be
implemented in the ULR first.
>   (2) A fully-featured test runner for SDKs who participate in the portability framework.
It thus complements the direct runners.
>   (3) A test runner for user code that depends on or customizes the runtime environment.
For example, a DoFn that shells out has a dependency that may be satisfied on the user's desktop
(and thus works fine on the direct runner), but perhaps not by the container harness image.
The ULR allows for an easy way to find out.
> The Java direct runner presumably has lots of pieces that can be reused.

This message was sent by Atlassian JIRA

View raw message