Asked about Moving data reliably
How do you handle an upstream schema change?
An answer that works
Validate incoming data against an expected schema and fail loudly rather than writing whatever arrived. Adding nullable columns is safe; removals and type changes need a versioned migration with both supported during the transition.
Reading an answer is not being able to give one. The section that teaches this is Moving data reliably, 5 hours of Data pipelines.
Learn this properlyAlso asked about Data pipelines
How do you make a data pipeline safe to rerun?What quality checks would you put in a pipeline?When would you choose streaming over batch?How do you handle late-arriving data?A daily job failed halfway and was restarted. Now some rows appear twice. How do you prevent this?How do you keep a RAG index up to date as documents change?