Databricks to Deprecate `downstream_impact` Column in Data Quality Monitoring
Databricks is deprecating the `downstream_impact` column found in the data quality monitoring results system table. Starting September 7, 2026, the column will gradually cease to be populated across regions. Users querying this system table should prepare for its removal, as the column will no longer contain data once the rollout is complete. This change affects how users track the downstream impact of data quality issues within their Databricks environments.
Deprecations (1) ›
- Deprecation of `downstream_impact` column in data quality monitoring
The `downstream_impact` column in the data quality monitoring results system table will be deprecated, with the rollout commencing on September 7, 2026. After this date, the column will no longer be populated in affected workspaces, requiring users to adjust any queries or processes that rely on this data.
https://docs.databricks.com/aws/en/release-notes/whats-coming#upcoming-deprecation-of-the-data-quality-monitoring-downstream_impact-column
Related releases
- Databricks Connector for Google Sheets Adds Write-Back to Unity Catalog Databricks Release Notes ·
- Databricks enables base environments for Python dependency management on classic compute (Beta) Databricks Release Notes ·
- Databricks to deprecate root_cause_analysis column in data quality monitoring results Databricks Release Notes ·
- Databricks Genie One Enhancements: Consistent Scheduled Tasks, PDF Export, and Mobile App Improvements Databricks Release Notes ·
- Databricks Lakeflow Connect Adds Workiva Connector (Beta) Databricks Release Notes ·
- Databricks RBAC to Default for Workspaces with Compliance Security Profile Databricks Release Notes ·