[
https://issues.apache.org/jira/browse/BEAM-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448517#comment-16448517
]
Bill Neubauer commented on BEAM-4124:
-------------------------------------
The protocol implementation is missing the ability to segment user messages
into sizes that fit into the physical channel. Java worked around this by
setting the limit to ~4G. We've preferred to keep the limit low since it hasn't
caused problems in practice yet. Are you noting this as a theoretical concern,
or is it getting in your way?
I don't mind bumping the max message size to 20M as a stopgap, but I'd like to
see more emphasis on developing segmentation since this is just not going to be
sustainable in the long run.
> Support elements larger than 4 MB
> ---------------------------------
>
> Key: BEAM-4124
> URL: https://issues.apache.org/jira/browse/BEAM-4124
> Project: Beam
> Issue Type: Bug
> Components: sdk-go
> Reporter: Cody Schroeder
> Assignee: Bill Neubauer
> Priority: Major
>
> The Go SDK harness is limited by a gRPC message size limit of 4 MB.
> https://github.com/apache/beam/blob/4a32353/sdks/go/pkg/beam/core/runtime/harness/datamgr.go#L31
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
