The short answer
Sources add, rename, or type-change columns. Pipelines must detect drift, avoid silent corruption, and evolve curated models safely.
Producer adds orders.discount_code
|
Ingestion lands new field in bronze (good: keep raw flexible)
|
Contract / schema check
- alert if unexpected break (type change, dropped column)
- allow additive fields if policy says so
|
Silver/gold models updated
- dbt model + tests
- backfill if historical values neededPractical playbook
- 1Land raw as-is ( or wide bronze) so you do not lose new fields.
- 2Detect drift: schema registry, Great Expectations, dbt tests, contract CI.
- 3Classify the change: additive (usually safe) vs breaking (rename/drop/type).
- 4Version contracts with producers when possible.
- 5Evolve silver/gold explicitly; do not auto-remap renames blindly.
- 6 if BI needs history for the new column.
Breaking change example
amount string → number. Gate the deploy, fix casts, validate samples, then promote.
Interview tip: Separate "absorb in raw" from "consciously evolve curated." Mention contracts and alerts so schema changes are not discovered by broken dashboards.