beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chinmaykolhatkar <>
Subject [GitHub] beam pull request #2216: [BEAM-831] ParDo Chaining of Apex Runner
Date Fri, 10 Mar 2017 07:05:08 GMT
GitHub user chinmaykolhatkar opened a pull request:

    [BEAM-831] ParDo Chaining of Apex Runner

    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`
     - [ ] 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.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](
    R: @tweise, @kennknowles 
    This is currently Work in Progress PR. The tests are being developed. This PR was created
to have a convenient environment for discussing this code. Here are the TODOS:
    1. Create the test cases for ParDo fusion for Apex runner

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

    $ git pull BEAM-831_ParDoChaining

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 #2216
commit d33532e607a5853f664602b3aae49c41a30bf046
Author: chinmaykolhatkar <>
Date:   2017-03-01T11:29:46Z

    [BEAM-831] ParDo Fusion of Apex Runner


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