Databricks schema changes break downstream pipelines
Data engineering2 posts from 2 people2d active+00 posts in the last 7 days, 0 the 7 days before (fading)Unverified
Posts per day
The posts behind it
2, newest first[v2 Bug] Spark snapshots leak numbered helper columns for list unique keys### Current Behavior The dbt v2 Spark snapshot materialization retains numbered `dbt_unique_key_N` staging helpers in both `missing_columns` and `source_columns` when `unique_key` is a list, including a one-item list such as `[id]`. Confirmed in the source at...dbt-labs/dbt · giacusOpen ↗Would you use JSONB or a separate document database for a product catalog?...JSON, inconsistent attribute names, validation, schema changes, or queries that became difficult to maintain?. And for those who moved the catalog to a document database, what made the separate system worthwhile?.r/SQL · u/OkShirt9372Open ↗
Companies and products named
About this problem
Evidence
2 posts from 2 people in 2 places, about 2 a week over 6 days. Mostly on dbt-labs/dbt, r/SQL. Tools named alongside: Apache Spark, dbt, GitHub, PostgreSQL.
Frustration Frustration 0 of 3· Seen on GitHub issues, Reddit
How it was grouped
Posts that state a pain and match the "schema-drift" rule about Databricks. First post Oct 2, 2026, latest Oct 7, 2026. Unverified: fewer than 3 posts, or one person or place only. Method
The same problem elsewhere
Other Databricks problems
Databricks users keep filing bugsDatabricks jobs fail silently or break oftenTrouble with Databricks catalogTrouble with Databricks incrementalBad data slips through Databricks unnoticedDatabricks login, SSO or OAuth breaksTrouble with Databricks sparkDatabricks upgrades break working setupsDatabricks rate limits and usage caps block workTrouble with Databricks tableTrouble with Databricks delta
History
Databricks schema changes break downstream pipelines (2 posts)