You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/12 03:51:02 UTC

[jira] [Updated] (BEAM-8145) Pubsub message size limit not taking size increase from base64 encoding into account

     [ https://issues.apache.org/jira/browse/BEAM-8145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-8145:
----------------------------------

This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.

> Pubsub message size limit not taking size increase from base64 encoding into account
> ------------------------------------------------------------------------------------
>
>                 Key: BEAM-8145
>                 URL: https://issues.apache.org/jira/browse/BEAM-8145
>             Project: Beam
>          Issue Type: Bug
>          Components: io-java-gcp
>            Reporter: Michael Yzvenn Wolanski
>            Priority: P3
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> In the PubSubIO, the default max batch size is set to `10 * 1024 * 1024` bytes. This however does not take into account the size increase of base64 encoding the messages after the flush. Base64 encodes each set of three bytes into four bytes.
> Therefore the 'true' size limit placed on the unencoded batch should be
> x = ((10 * 1024 * 1024) / 4) * 3 = 7864320 bytes



--
This message was sent by Atlassian Jira
(v8.20.1#820001)