GitHub user tgroh opened a pull request:
https://github.com/apache/incubator-beam/pull/992
[BEAM-469] Do not modify the context in NullableCoder
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-] 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 `` 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.txt).
---
The NullableCoder does not encode any elements after the subcoder
encodes the input value for non-null values. As a result, the subcoder
should see the entire input stream if it is available.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tgroh/incubator-beam nullable_non_nested
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-beam/pull/992.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 #992
commit e9737ed446bd7c3ba566a3cf148b6a29bcb544c8
Author: Thomas Groh
Date: 2016-09-23T15:58:07Z
Do not modify the context in NullableCoder
The NullableCoder does not encode any elements after the subcoder
encodes the input value for non-null values. As a result, the subcoder
should see the entire input stream if it is available.
---
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.
---