beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kennknowles <>
Subject [GitHub] incubator-beam pull request: [BEAM-259] Configure RunnableOnServic...
Date Thu, 05 May 2016 22:24:58 GMT
GitHub user kennknowles opened a pull request:

    [BEAM-259] Configure RunnableOnService tests for Spark runner, batch mode

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [x] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [x] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [x] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [x] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](
    This PR demonstrates how to configure the integration tests. It has two categories of
    1. Transforms that are not supported. For these we can add surefire exclusions for now.
    2. Runtime errors having to do with configuring Spark. I'm hoping someone with expertise
in the runner can take quickly recommend the course of action.

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

    $ git pull spark-integration

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 #294
commit d8a2a34f723ff4ca7fe841c8056706c19d37770d
Author: Kenneth Knowles <>
Date:   2016-05-05T22:11:07Z

    Configure RunnableOnService tests for Spark runner, batch mode


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message