beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kennknowles <>
Subject [GitHub] beam pull request #2147: [BEAM-1611] Explicitly GBK before stateful ParDo in...
Date Thu, 02 Mar 2017 23:33:07 GMT
GitHub user kennknowles opened a pull request:

    [BEAM-1611] Explicitly GBK before stateful ParDo in Dataflow batch

    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`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [ ] 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](

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

    $ git pull state-issue

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 #2147
commit 2cfcac27bbf961f3dd017701b0eee9160a4a847d
Author: Kenneth Knowles <>
Date:   2017-03-02T22:29:56Z

    In Dataflow batch, explicitly GroupByKey before a stateful ParDo

commit 15a781cbb280341e863bccac04332965797572a1
Author: Kenneth Knowles <>
Date:   2017-03-02T22:48:26Z

    Add test for deduping by key with stateful ParDo

commit be4271c3a5cadbb92dfbb707fb1f50a486bca827
Author: Kenneth Knowles <>
Date:   2017-03-02T22:57:42Z

    HACK: use ParDo multi until it is the only thing


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