beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From staslev <>
Subject [GitHub] beam pull request #2357: Added a specific signature so that Kryo doesn't hav...
Date Wed, 29 Mar 2017 12:34:03 GMT
GitHub user staslev opened a pull request:

    Added a specific signature so that Kryo doesn't have to look for it u…

    …sing reflective exploration.
    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 optimised-StatelessJavaSerializer

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 #2357
commit 92ee1b56b451e9a3545a957e72dd97f688197ee4
Author: Stas Levin <>
Date:   2017-03-29T12:33:17Z

    Added a specific signature so that Kryo doesn't have to look for it using reflective exploration.


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