kennknowles opened a new issue, #18901:
URL: https://github.com/apache/beam/issues/18901

   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.
   
   Imported from Jira 
[BEAM-4459](https://issues.apache.org/jira/browse/BEAM-4459). Original Jira may 
contain additional context.
   Reported by: reuvenlax.
   Subtask of issue #18898


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to