Details
-
Sub-task
-
Status: Open
-
P3
-
Resolution: Unresolved
-
None
-
None
-
None
Description
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.