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 21:13:00 UTC

[jira] [Commented] (BEAM-4459) Schemas across pipeline modifications

    [ https://issues.apache.org/jira/browse/BEAM-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17547118#comment-17547118 ] 

Kenneth Knowles commented on BEAM-4459:
---------------------------------------

This issue has been migrated to https://github.com/apache/beam/issues/18901

> Schemas across pipeline modifications
> -------------------------------------
>
>                 Key: BEAM-4459
>                 URL: https://issues.apache.org/jira/browse/BEAM-4459
>             Project: Beam
>          Issue Type: Sub-task
>          Components: io-java-gcp
>            Reporter: Reuven Lax
>            Priority: P3
>
> As per the snapshot/update proposal, we want to be able to update pipelines without damaging the in-flight state. Since schema fields might get reordered on update, we must ensure that the old mappings are preserved. This will require us to have two ids - the logical ids the user interfaces with (which might change), and the physical index where we store the schema.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)