GitHub user vikkyrk opened a pull request:
https://github.com/apache/beam/pull/3586
Increase the gRPC message size to max value
Follow this checklist to help us incorporate your contribution quickly and
easily:
- [ ] 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.
- [ ] Each commit in the pull request should have a meaningful subject
line and body.
- [ ] Format the pull request title like `[BEAM-1234] Fixes bug in
ApproximateQuantiles`, where you replace `BEAM-1234` 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 Agreement](https://www.apache.org/licenses/icla.pdf).
---
The default message size that can be sent or received over gRPC is 4MB. For
the fn API case we do buffering at a layer above, so setting the message size
at the gRPC level to a max value.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vikkyrk/incubator-beam msg_size
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/3586.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 #3586
----
commit 2814ed32b79c53451635b8cbc5b264b2f6c0837c
Author: Vikas Kedigehalli <[email protected]>
Date: 2017-07-18T17:06:46Z
Increase the gRPC message size to max value
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
