beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robertwb <>
Subject [GitHub] incubator-beam pull request #683: More efficient default coder.
Date Mon, 18 Jul 2016 22:09:04 GMT
GitHub user robertwb opened a pull request:

    More efficient default coder.

    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 fast-coder

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 #683
commit 4c8e4fdac2a46b381a649728d2a5cdc4551d8a50
Author: Robert Bradshaw <>
Date:   2016-07-12T22:58:56Z

    Implement coder optimized for coding primitives.
    This coder falls back to another coder (e.g. PickleCoder)
    for other types, but is much faster for ints, strings, etc.

commit 6ffb3d25005834504d7504e0889c04e47bc969e9
Author: Robert Bradshaw <>
Date:   2016-07-18T21:25:08Z

    Used fast primitives coder as fallback coder.

commit 687315e8b8ed1dc91d89afe9bfa61feb98ecf455
Author: Robert Bradshaw <>
Date:   2016-07-18T22:07:53Z

    Add fast support for dicts for default coder.


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