GitHub user tweise opened a pull request:
https://github.com/apache/beam/pull/2473
[BEAM-1053] ApexGroupByKeyOperator serialization issues
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](https://www.apache.org/licenses/icla.pdf).
---
R: @jkff
Probably this code will go away after the SDF work but this bug is trivial
to fix and has been there for a while, so let's close it out separately. For
stateInternals it was already addressed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tweise/beam
BEAM-1053_ApexGroupByKeySerialization
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/2473.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2473
----
commit adf378568e7c676c3b2780c07caae679ea461f01
Author: Thomas Weise <t...@apache.org>
Date: 2017-04-08T20:01:01Z
BEAM-1053 ApexGroupByKeyOperator serialization issues
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
