beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From evindj <>
Subject [GitHub] beam pull request #3643: [Beam-2482] - CodedValueMutationDetector should use...
Date Wed, 26 Jul 2017 04:54:15 GMT
GitHub user evindj opened a pull request:

    [Beam-2482] - CodedValueMutationDetector should use the coders structural value

    Follow this checklist to help us incorporate your contribution quickly and easily:
     - [ ] Make sure there is a [JIRA issue](
filed for the change (usually before you start working on it).  Trivial changes like typos
do not require a JIRA issue.  Your pull request should address just this issue, without pulling
in other changes.
     - [ ] Each commit in the pull request should have a meaningful subject line and body.
     - [ ] Format the pull request title like `[BEAM-XXX] Fixes bug in ApproximateQuantiles`,
where you replace `BEAM-XXX` with the appropriate JIRA issue.
     - [ ] Write a pull request description that is detailed enough to understand what the
pull request does, how, and why.
     - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will
be performed on your pull request automatically.
     - [ ] If this contribution is large, please file an Apache [Individual Contributor License

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

    $ git pull BEAM-2482

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 #3643
commit 3aa0fc37d96b6e76dbc540fc0fb538a438cbf6e9
Author: Innocent Djiofack <>
Date:   2017-07-26T03:41:02Z

    Changed the mutation detector to be based on structural value only

commit 36c7a14c69ba628f477798f63d4e721dc86e2be7
Author: Innocent Djiofack <>
Date:   2017-07-26T04:51:21Z

    fixed compilation errors and a bug in ByteArraycoder


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