You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Brian Hulette (Jira)" <ji...@apache.org> on 2021/03/16 21:19:00 UTC
[jira] [Updated] (BEAM-10277) beam:coder:row:v1 implementations
should respect encoding_position
[ https://issues.apache.org/jira/browse/BEAM-10277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Hulette updated BEAM-10277:
---------------------------------
Description: row coder implementations (Java, Python, and Go) should use the encoding position to determine the order in which to encode/decode fields. This will allow runners to re-order fields to maintain compatibility when schemas change in a pipeline update. (was: row coder implementations should use the encoding position to determine the order in which to encode/decode fields. This will allow runners to re-order fields to maintain compatibility when schemas change in a pipeline update.)
> beam:coder:row:v1 implementations should respect encoding_position
> ------------------------------------------------------------------
>
> Key: BEAM-10277
> URL: https://issues.apache.org/jira/browse/BEAM-10277
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core, sdk-py-core
> Reporter: Brian Hulette
> Priority: P3
> Labels: Clarified
>
> row coder implementations (Java, Python, and Go) should use the encoding position to determine the order in which to encode/decode fields. This will allow runners to re-order fields to maintain compatibility when schemas change in a pipeline update.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)