We just had a major upstream schema change break all our dbt models, so what is the quickest way to handle schema drift in pipelines without losing historical data today?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
We just had a major upstream schema change break all our dbt models, so what is the quickest way to handle schema drift in pipelines without losing historical data today?
1 real search · 1 real-search pass
dbt documentation incremental models on_schema_change append_new_columns sync_all_columns historical data snapshots schema changesGoogle ↗
OBSERVED
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 1 queries…
Searches and sources
ChatGPT1 real searches · gpt-6
dbt documentation incremental models on_schema_change append_new_columns sync_all_columns historical data snapshots schema changes Google ↗
- Configure incremental models · docs.getdbt.com
- Choosing incremental models or snapshots · docs.getdbt.com
- Add snapshots to your DAG · docs.getdbt.com