OpenSharing (formerly Delta Sharing)

Databricks · Unity Catalog & Governance

Theory

OpenSharing, formerly Delta Sharing, is Databricks' open protocol for sharing live data securely with other teams and companies without copying it. The provider creates a share, a read-only collection of tables, views, volumes, models or notebooks, and a recipient that represents the consumer. Granting the share to the recipient lets the consumer read the current data directly from the provider's storage, governed by Unity Catalog.

There are two flavours. Databricks-to-Databricks sharing connects two Unity Catalog metastores: the recipient is identified by its sharing identifier and mounts the share as a catalog. Open sharing (Databricks-to-Open) gives a bearer-token credential file so non-Databricks tools such as pandas, Power BI or Spark elsewhere can read the data. For example, TechTown shares main.sales.orders with a partner as share partner_sales; the partner queries it as a read-only catalog and always sees today's data.

Why we use it

Emailing CSV extracts or copying data to FTP creates stale, ungoverned copies. OpenSharing gives partners and other business units live, read-only access that you can audit and revoke, without moving data into another platform.

When to use it

Use it for sharing across organizations, clouds, regions or metastores. Inside one metastore, plain GRANT statements are simpler. Consumers who want to discover public or paid datasets use Databricks Marketplace, which is built on the same sharing technology.

How it works

  1. Provider creates a share
  2. Add tables, views or volumes to the share
  3. Create a recipient
  4. Does the recipient use Databricks with Unity Catalog? Yes: Databricks-to-Databricks: use their sharing identifier. No: Open sharing: send the token credential file.
  5. GRANT SELECT ON SHARE to the recipient
  6. Recipient queries live, read-only data

Syntax

CREATE SHARE name
ALTER SHARE name ADD TABLE main.sales.orders [WITH HISTORY]
CREATE RECIPIENT name [USING ID '<sharing-identifier>']
GRANT SELECT ON SHARE name TO RECIPIENT recipient
SHOW ALL IN SHARE name | DESCRIBE RECIPIENT name
Recipient side: CREATE CATALOG c USING SHARE provider.share

Example

-- Provider workspace
CREATE SHARE IF NOT EXISTS partner_sales
  COMMENT 'Orders for Pune distributor';

ALTER SHARE partner_sales ADD TABLE main.sales.orders;

CREATE RECIPIENT IF NOT EXISTS pune_distributor
  USING ID 'aws:ap-south-1:<metastore-uuid>';   -- Databricks-to-Databricks

GRANT SELECT ON SHARE partner_sales TO RECIPIENT pune_distributor;

-- Recipient workspace
CREATE CATALOG techtown_shared USING SHARE techtown.partner_sales;
SELECT region, SUM(amount) FROM techtown_shared.sales.orders GROUP BY region;

Key points

Databricks topics

Databricks Fundamentals

Compute

Notebooks & Development

Apache Spark on Databricks

Delta Lake

Unity Catalog & Governance

Data Ingestion

Declarative Pipelines (Lakeflow)

Lakeflow Jobs

Databricks SQL & BI

Architecture, Performance & Cost

Machine Learning & AI

Certification & Interview

T
Tech Town
Log InSign Up Free
Home SQL Python DSA Power BI Snowflake Databricks Spark Gen AI Practice Problems Contest Blog

Master Databricks

The lakehouse platform from the ground up: Apache Spark, Delta Lake, Unity Catalog, Lakeflow pipelines and jobs, Databricks SQL and MLflow. Click any topic in the sidebar to open it right here.

{{ sectionCount }}
Sections
{{ topicCount }}
Topics
Free
Forever
Hands-on practice Practice SQL / Spark SQL Sharpen the SQL you use in Databricks SQL and Spark SQL: 150 query problems in a live editor with instant checking. Start practising →
Section {{ sec.num }}

{{ sec.label }}

Databricks  /  {{ current.sectionLabel }}  /  {{ current.name }}

{{ current.name }}

Theory

{{ current.def }}

Why we use it

{{ rich.why }}

When to use it

{{ rich.when }}

{{ sec.h }}

{{ sec.body }}

{{ sec.body }}

Diagram

{{ rich.dg.caption }}

{{ tb.title }}
{{ c.v }}
{{ rich.dg.op }}
➜
{{ rich.dg.output.title }}
{{ c.v }}
{{ nd.label }}
{{ nd.sub }}
{{ nd.label }}
{{ nd.sub }}
{{ rich.dg.left.title }}
{{ it }}
{{ rich.dg.right.title }}
{{ it }}
On screen — where to click

{{ rich.ui.title }}

{{ u.text }}
  1. {{ st.n }}{{ st.text }}
{{ rich.ui.title }}
{{ u.text }}
Flowchart — how it works
{{ nd.text }}
{{ nd.text }}
◇ {{ nd.text }}
Yes → {{ nd.yes }}
No → {{ nd.no }}
Syntax
{{ current.syntax }}
Example
{{ current.example }}
Want to run this yourself? Databricks needs a real workspace — there's no in-browser engine for it. Click Copy above, then paste it into a notebook or the SQL editor in Databricks Free Edition (free, no credit card) and run it on serverless compute.
Key Points — click to check off as you learn
  • {{ pt.mark }} {{ pt.text }}

Share this topic