beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tgroh <>
Subject [GitHub] incubator-beam pull request #689: Express ParDo.Bound in terms of ParDo.Boun...
Date Tue, 19 Jul 2016 17:42:36 GMT
GitHub user tgroh opened a pull request:

    Express ParDo.Bound in terms of ParDo.BoundMulti

    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](
    This simplifies the set of primitives required to implement the Beam

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

    $ git pull no_par_do_single

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 #689
commit 84d74d95e075cb5d365bfcb003abb53215c622d9
Author: Thomas Groh <>
Date:   2016-07-19T16:41:34Z

    Propagate Coder in WithTimestamps
    The same coder should be used, in case it was explicitly set. Coder
    inference can already have happened.

commit b04a3833a3fd754e3f49eaa49b4831c6abfee322
Author: Thomas Groh <>
Date:   2016-07-19T17:40:24Z

    Express ParDo.Bound in terms of ParDo.BoundMulti
    This simplifies the set of primitives required to implement the Beam


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