Skip to content

Databricks releases, every cloud

All GAPreviewBehavior changeDeprecationUpdate

6 releases of 1321

Last updated

  1. Query text is now masked by default in system tables and APIs

    Masking applies to system.query.history, Query History API, and List Queries API. Account admins can grant access to unmasked text via databricks_pii_access group.

    #Audit logs#Security
    AWS, read it on their docsAzure, read it on their docsGCP, read it on their docsSAP(unknown)
  2. Lakebase is enabled by default in compliance security profile workspaces

    Replaces manual Lakebase enablement in HIPAA, C5, or TISAX workspaces.

    #Lakebase
    AWS, read it on their docsAzure, read it on their docsGCP(not on this cloud)SAP(unknown)
  3. Postgres password authentication is now disabled by default for new Lakebase projects

    Existing projects are unaffected, enable in project settings to allow.

    #Lakebase#Security
    AWS, read it on their docsAzure, read it on their docsGCP(not on this cloud)SAP(not on this cloud)
  4. New Lakebase instances now scale to zero by default

    New instances scale to zero after 24 hours of inactivity, reducing compute costs. Existing projects are unaffected.

    #Lakebase
    AWS, read it on their docsAzure, read it on their docsGCP(not on this cloud)SAP(not on this cloud)
  5. New Lakebase instances include autoscaling by default

    Autoscaling is on by default for new instances, applies to UI, API, Terraform, and SDK creations.

    #Lakebase
    AWS, read it on their docsAzure, read it on their docsGCP(not on this cloud)SAP(not on this cloud)
  6. The sourceIpAddress field in audit logs will no longer include a port number Coming soon

    Removes port number, which was always 0, for consistency with other logs.

    #Audit logs
    AWS, read it on their docsAzure, read it on their docsGCP, read it on their docsSAP(unknown)
  7. Run the change, do not just read it. Hands-on labs in your own Databricks workspace, graded when you submit. Browse labs

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.