beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lukecwik <>
Subject [GitHub] beam pull request #1717: [BEAM-1231] Use well known coder types in Java
Date Thu, 29 Dec 2016 22:36:36 GMT
GitHub user lukecwik opened a pull request:

    [BEAM-1231] Use well known coder types in Java

    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.
     - [ ] 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 java_well_known_coders

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 #1717
commit 71d2a6eb3f9b654becfaa43d6b218f36f6928708
Author: Luke Cwik <>
Date:   2016-12-29T20:03:31Z

    [BEAM-1231] Use well known coder types in Java

commit 5b614dece8babcad5b9a087e969d143212be0a3d
Author: Luke Cwik <>
Date:   2016-12-29T21:39:45Z

    Swap to use initializeCloudObject as customization point for CloudObjects.
    Hide StandardCoder#getComponents() and have coders only rely on Coder#getCoderArguments()

commit ad061a7c4e696d6407d6d209ff7e35933c9fc71b
Author: Luke Cwik <>
Date:   2016-12-29T22:20:04Z

    Use kind:* for certain well known coder types.

commit b927e68afbaa35f8dac939e39b93b8dc9c224e66
Author: Luke Cwik <>
Date:   2016-12-29T22:31:19Z

    fixup! Minor formatting/comment changes


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