Databricks releases, every cloud
- Automatic change data feed will soon be available in all supported regions Coming soon
Requires Databricks Runtime 19 or above with row tracking enabled. Replaces manual change data feed setup on tables.
- Environment variables for serverless jobs are in Beta
Requires workspace admin to enable from Previews page.
- Transactions are now generally available
Require catalog commits enabled on participating tables. Use BEGIN ATOMIC or BEGIN TRANSACTION syntax.
- Variant and Variant shredding are now generally available
Requires Databricks Runtime 17.3, recommended 18.1 for optimal performance.
- Variant will soon be available by default for workspaces with the compliance security profile enabled Coming soon
Ingests semi-structured data from sources like Kinesis and REST APIs. Available in July 2026.
AWS, read it on their docsAzure, read it on their docsGCP, read it on their docsSAP(not on this cloud) - Scala and Java UDFs in Unity Catalog are now generally available
Reuses existing JVM logic, offers better performance than Python UDFs.
- Run the change, do not just read it. Hands-on labs in your own Databricks workspace, graded when you submit. Browse labs
- Automatic upgrades will roll out more features to existing tables Coming soon
Adds row tracking and Checkpoint V2 to existing tables.
AWS, read it on their docsAzure, read it on their docsGCP, read it on their docsSAP(not on this cloud) - Object metadata column is now in Public Preview
Exposes object properties like MIME type and tags, available in Databricks Runtime 18.1.
AWS, read it on their docsAzure, read it on their docsGCP, read it on their docsSAP(not on this cloud) - MySQL integrated CDC pipeline is now in Beta
Replaces separate ingestion gateway, requires single pipeline update.
AWS, read it on their docsAzure, read it on their docsGCP, read it on their docsSAP(not on this cloud) - Parquet v2 for Delta Lake tables is generally available
Requires Databricks Runtime 18.1 and above, set delta.parquet.format.version to 2.12.0.
- AUTO CDC flows for streaming tables in Databricks SQL are generally available
Automatically handles out-of-order records as SCD type 1 or 2, replacing complex MERGE INTO logic.
AWS, read it on their docsAzure, read it on their docsGCP, read it on their docsSAP(not on this cloud) - Auto time-to-live for automatic row deletion is generally available
Deletes rows from Delta Lake, Iceberg, and streaming tables based on a DATE or TIMESTAMP column.
- Converting a partitioned table to liquid clustering is generally available
Uses ALTER TABLE command, requires Databricks Runtime 18.1 or above.
- Lakehouse Replay (Beta)
Automatically replays serverless workloads against upcoming runtime releases. Requires no setup.
AWS, read it on their docsAzure, read it on their docsGCP, read it on their docsSAP(not on this cloud) - Catalog commits are now generally available
Enables multi-statement transactions on Unity Catalog managed Delta tables, supported by products like MLflow and Delta Sharing.
- Spark Declarative Pipelines on Lakeflow updates are retained for 60 days
Retention period increased from 30 to 60 days, applying to UI and REST API updates.
AWS, read it on their docsAzure, read it on their docsGCP, read it on their docsSAP(not on this cloud) - SQL alert task for jobs (Beta)
Evaluates SQL alerts as part of workflows, enabling automated condition checks and notifications.
AWS, read it on their docsAzure, read it on their docsGCP, read it on their docsSAP(not on this cloud) - Multi-table transactions are now in Public Preview
Requires catalog commits on participating tables, supports Unity Catalog managed Delta tables.
AWS, read it on their docsAzure, read it on their docsGCP, read it on their docsSAP(not on this cloud) - Get this table by email. One Monday mail covering the week, filtered to the clouds and products you run. Weekly digest
- Zstd is now the default compression for new managed tables
Replaces Snappy compression, applies to Databricks Runtime 16.0 and above.
Headlines, dates and product areas are Databricks' own, from the release notes published for each cloud, and every item links to the note it came from. The one-line summaries are ours. Not a Databricks product and not affiliated with Databricks, Inc.