[ https://issues.apache.org/jira/browse/BEAM-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Beam JIRA Bot reassigned BEAM-4459: ----------------------------------- Assignee: (was: Reuven Lax) > 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-assigned > > 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)