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/06/03 20:15:00 UTC
[jira] [Commented] (BEAM-3401) Fully specify the length prefix coder
[ https://issues.apache.org/jira/browse/BEAM-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17546889#comment-17546889 ]
Kenneth Knowles commented on BEAM-3401:
---------------------------------------
This issue has been migrated to https://github.com/apache/beam/issues/18701
> Fully specify the length prefix coder
> -------------------------------------
>
> Key: BEAM-3401
> URL: https://issues.apache.org/jira/browse/BEAM-3401
> Project: Beam
> Issue Type: Improvement
> Components: sdk-go, sdk-java-core, sdk-py-core
> Reporter: Luke Cwik
> Priority: P3
> Labels: Clarified, portability
>
> Choose a variable integer encoding that is efficient in encoding/decoding speed out of one of the many variants like LEB128 / PrefixVarint / SQLite varint
> Also update the length prefix encoding to be parameterized by a block size so that the entire object doesn't have to be written in memory as per [http://doc/1IGduUqmhWDi_69l9nG8kw73HZ5WI5wOps9Tshl5wpQA/edit#heading=h.j8zpiclux4id]
> Add cross language validation tests for encoding/decoding to [https://github.com/apache/beam/blob/master/sdks/python/apache_beam/testing/data/standard_coders.yaml]
> Document the format explicitly and choose a stable URN.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)