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

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

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

Beam JIRA Bot commented on BEAM-4459:
-------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> 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: P2
>              Labels: stale-P2
>
> 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.3.4#803005)