beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tweise <>
Subject [GitHub] beam pull request #2927: [BEAM-831] ParDo Chaining of Apex Runner
Date Fri, 05 May 2017 21:33:30 GMT
GitHub user tweise 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:
     - [ ] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`.
     - [ ] 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: @kennknowles 
    based on #2216 

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

    [BEAM-831] ParDo Fusion of Apex Runner

commit cad694ae0f641b69e3a12eb15b82a3234b793216
Author: Thomas Weise <>
Date:   2017-05-05T13:45:34Z

    [BEAM-831] Adjustments to the chaining logic.
    closes #2216


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