← All updates Databricks Update One-Pager Navy version
databricks Platform · Updated Jun 3, 2025

History sharing now enabled by default to improve table read performance for…

History sharing is enabled by default (for Databricks Runtime 16.2 and above) to improve table read performance for Databricks to Databricks Delta Sharing.

Update Open docs ↗release note ↗
What it does

History sharing is enabled by default (for Databricks Runtime 16.2 and above) to improve table read performance for Databricks to Databricks Delta Sharing. This page gives an overview of how to use Databricks to Databricks OpenSharing to share data securely with any Databricks user, regardless of account or cloud host, as long as that user has access to a workspace enabled for Unity Catalog. Who should use Databricks to Databricks OpenSharing?

Why it matters

History sharing is enabled by default (for Databricks Runtime 16.2 and above) to improve table read performance for Databricks to Databricks Delta Sharing.

Key capabilities
A commercial cloud shares to
A commercial cloud shares to or receives shares from either AWS GovCloud or AWS GovCloud DoD.
AWS GovCloud and AWS GovCloud
AWS GovCloud and AWS GovCloud DoD share with each other.
Architecture
Databricks Platform → Platform
In short

History sharing is enabled by default (for Databricks Runtime 16.2 and above) to improve table read performance for Databricks to Databricks Delta Sharing. This page gives an overview of how to use Databricks to Databricks OpenSharing to share data securely…

Read the full documentation ↗
Key takeaway
History sharing is enabled by default (for Databricks Runtime 16.2 and above) to improve table read performance for Databricks to Databricks Delta Sharing.
2025-06-03-865e8332 Generated by the Databricks Updates Agent · browse all updates