Real ChatGPT answer · index seedeqIAk2MrPTscompleteB2B software · data and analytics platformsinformational
What is the modern data stack consensus on handling columns that get deleted from source databases without breaking downstream reporting models
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
What is the modern data stack consensus on handling columns that get deleted from source databases without breaking downstream reporting models
3 real searches · 1 real-search pass
dbt source schema changes deleted columns downstream models contract deprecation schema evolution best practicesGoogle ↗
OBSERVED
data warehouse schema evolution handling dropped columns source tables backward compatibility analytics engineeringGoogle ↗
OBSERVED
Fivetran dropped columns soft delete schema changes downstream dbt modelsGoogle ↗
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 3 queries…
Searches and sources
ChatGPT3 real searches · gpt-6
dbt source schema changes deleted columns downstream models contract deprecation schema evolution best practices Google ↗
data warehouse schema evolution handling dropped columns source tables backward compatibility analytics engineering Google ↗
Fivetran dropped columns soft delete schema changes downstream dbt models Google ↗
- Why Do Deleted Source Columns Still Appear in the Destination? · fivetran.com
- How to Think About Schema Changes | Blog · fivetran.com
- Schema evolution in Databricks · docs.databricks.com
- Model versions · docs.getdbt.com
- versions · docs.getdbt.com
- Column-level lineage · docs.getdbt.com
Queries
3 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
dbt source schema changes deleted columns downstream models contract deprecation schema evolution best practices OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
data warehouse schema evolution handling dropped columns source tables backward compatibility analytics engineering OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
Fivetran dropped columns soft delete schema changes downstream dbt models OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 |