Research FIELD GUIDE 06
FIELD GUIDE 06
Operating model and exit
Measure operating effort and prove that the rollback can work.
Put the ongoing work in the comparison.
Count release testing, connector updates, schema changes, entitlement reviews, incident handling and cost allocation. Include recurring transfers and full copies. Use a common demand horizon and label the assumption that contributes most to the result.
Agree on the point of no return.
Specify the last known snapshot, the maximum acceptable data lag and the threshold for rollback. Reconcile changes written after cutover before sending any consumer back to the previous system.
Record what leaves with the workload.
Inventory table metadata, catalog mappings, policies, lineage, logs and any platform-native functions. Identify what can be exported, what has to be rewritten and what another operator must be able to inspect.
Primary references
- SpecificationApache Iceberg table format specification
- StandardOpenLineage project and metadata model
- DatabricksUnity Catalog and the open lakehouse