GitHub user kennknowles opened a pull request:
https://github.com/apache/beam/pull/3887
[BEAM-2884] Revert "This closes #3859: Send portable protos for ParDo in
DataflowRunner"
Follow this checklist to help us incorporate your contribution quickly and
easily:
- [x] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/projects/BEAM/issues/) 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.
- [x] Each commit in the pull request should have a meaningful subject
line and body.
- [x] Format the pull request title like `[BEAM-XXX] Fixes bug in
ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA
issue.
- [x] Write a pull request description that is detailed enough to
understand what the pull request does, how, and why.
- [x] Run `mvn clean verify` to make sure basic checks pass. A more
thorough check will be performed on your pull request automatically.
- [x] If this contribution is large, please file an Apache [Individual
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
---
The blowup to the job submission was a bit much. We will instead wait to
implement a more robust longer-term solution that does not embed the protos
directly in the job submission.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kennknowles/beam ParDoPayload-rollback
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/3887.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 #3887
----
commit cf665b6113be7f01fcb55e80d3657079055b8f95
Author: Kenneth Knowles <k...@google.com>
Date: 2017-09-22T18:34:28Z
Revert "This closes #3859: [BEAM-2884] Send portable protos for ParDo in
DataflowRunner"
This reverts commit 0d5d00d7060d6e4ee8273201e3432f14abf35f8a, reversing
changes made to 4e4d102124576aefc3f71e432dbf6197aaaa92e3.
The blowup to the job submission was a bit much. We will instead wait to
implement a more robust longer-term solution that does not embed the protos
directly in the job submission.
----
---
