Create and manage shares for Delta Sharing

This article explains how to create and manage shares for Delta Sharing.

A share is a securable object in Unity Catalog that you can use for sharing the following data assets with one or more recipients:

Tables and table partitions
Views, including dynamic views that restrict access at the row and column level
Volumes
Notebooks
AI models

If you share an entire schema (database), the recipient can access all of the tables, views, models, and volumes in the schema at the moment you share it, along with any data and AI assets that are added to the schema in the future.

A share can contain data and AI assets from only one Unity Catalog metastore. You can add or remove data and AI assets from a share at any time.

For more information, see Shares, providers, and recipients.

Requirements

To create a share, you must:

Be a metastore admin or have the CREATE SHARE privilege for the Unity Catalog metastore where the data you want to share is registered.
Create the share using a Databricks workspace that has that Unity Catalog metastore attached.

To add tables or views to a share, you must:

Be the share owner.
Have the USE CATALOG and USE SCHEMA privilege on the catalog and schema that contain the table or view, or ownership of the catalog or schema.
Have the SELECT privilege on the table or view. You must keep that privilege in order for the table or view to continue to be shared. If you lose it, the recipient cannot access the table or view through the share. Databricks therefore recommends that you use a group as the share owner.

To add volumes to a share, you must:

Be the share owner.
Have the USE CATALOG and USE SCHEMA privilege on the catalog and schema that contain the volume, or ownership of the catalog or schema.
Have the READ VOLUME privilege on the volume. You must keep that privilege in order for the volume to continue to be shared. If you lose it, the recipient cannot access the volume through the share. Databricks therefore recommends that you use a group as the share owner.

To add models to a share, you must:

Be the share owner.
Have the USE CATALOG and USE SCHEMA privilege on the catalog and schema that contain the model, or ownership of the catalog or schema.
Have the EXECUTE privilege on the model. You must keep that privilege in order for the model to continue to be shared. If you lose it, the recipient cannot access the model through the share. Databricks therefore recommends that you use a group as the share owner.

To share an entire schema, you must:

Be the share owner and the schema owner, or have USE SCHEMA.
Have SELECT on the schema to share tables.
Have READ VOLUME on the schema to share volumes.

To add notebook files to a share, you must be:

The share owner and have CAN READ permission on the notebook.

To grant recipient access to a share, you must be one of these:

Metastore admin.
User with delegated permissions or ownership on both the share and the recipient objects ((USE SHARE + SET SHARE PERMISSION) or share owner) AND (USE RECIPIENT or recipient owner).

To view shares, you must be one of these:

A metastore admin (can view all)
A user with the USE SHARE privilege (can view all)
The share object owner

Compute requirements:

If you use a Databricks notebook to create the share, your cluster must use Databricks Runtime 11.3 LTS or above and the shared or single user cluster access mode.
If you use SQL statements to add a schema to a share (or update or remove a schema), you must use a SQL warehouse or compute running Databricks Runtime 13.3 LTS or above. Doing the same using Catalog Explorer has no compute requirements.

Add tables to a share

To add tables to a share, you can use Catalog Explorer, the Databricks Unity Catalog CLI, or SQL commands in a Databricks notebook or the Databricks SQL query editor.

Note

Table comments, column comments, and primary key constraints are included in shares that are shared with a recipient using Databricks-to-Databricks sharing on or after July 25, 2024. If you want to start sharing comments and constraints through a share that was shared with a recipient before the release date, you must revoke and re-grant recipient access to trigger comment and constraint sharing.

Permissions required: Owner of the share object, USE CATALOG and USE SCHEMA on the catalog and schema that contain the table, and the SELECT privilege on the table. You must maintain the SELECT privilege for as long as you want to share the table. For more information, see Requirements.

Note

If you are a workspace admin and you inherited the USE SCHEMA and USE CATALOG permissions on the schema and catalog that contain the table from the workspace admin group, then you cannot add the table to a share. You must first grant yourself the USE SCHEMA and USE CATALOG permissions on the schema and catalog.

In your Databricks workspace, click Catalog.
At the top of the Catalog pane, click the gear icon and select Delta Sharing.

Alternatively, from the Quick access page, click the Delta Sharing > button.
On the Shared by me tab, find the share you want to add a table to and click its name.
Click Manage assets > Add data assets.
On the Add tables page, select either an entire schema (database) or individual tables and views.
- To select a table or view, first select the catalog, then the schema that contains the table or view, then the table or view itself.
  
  You can search for tables by name, column name, or comment using workspace search. See Search for workspace objects.
- To select a schema, first select the catalog and then the schema.
  
  For detailed information about sharing schemas, see Add schemas to a share.
History: Share the table history to allow recipients to perform time travel queries or read the table with Spark Structured Streaming. For Databricks-to-Databricks shares, the table’s Delta log is also shared to improve performance. See Improve table read performance with history sharing. History sharing requires Databricks Runtime 12.2 LTS or above.

Note

If, in addition to doing time travel queries and streaming reads, you want your customers to be able to query a table’s change data feed (CDF) using the table_changes() function, you must enable CDF on the table before you share it WITH HISTORY.
(Optional) Click Advanced table options to specify the following options. Alias and partitions are not available if you select an entire schema. Table history is included by default if you select an entire schema.
- Alias: An alternate table name to make the table name more readable. The alias is the table name that the recipient sees and must use in queries. Recipients cannot use the actual table name if an alias is specified.
- Partition: Share only part of the table. For example, (column = 'value'). See Specify table partitions to share and Use recipient properties to do partition filtering.
Click Save.

Run the following command in a notebook or the Databricks SQL query editor to add a table:

ALTER SHARE <share-name> ADD TABLE <catalog-name>.<schema-name>.<table-name>  [COMMENT "<comment>"]
   [PARTITION(<clause>)] [AS <alias>]
   [WITH HISTORY | WITHOUT HISTORY];

Run the following to add an entire schema. The ADD SCHEMA command requires a SQL warehouse or compute running Databricks Runtime 13.3 LTS or above. For detailed information about sharing schemas, see Add schemas to a share.

ALTER SHARE <share-name> ADD SCHEMA <catalog-name>.<schema-name>
[COMMENT "<comment>"];

Options include the following. PARTITION and AS <alias> are not available if you select an entire schema. WITH HISTORY is selected by default for all tables if you select an entire schema.

PARTITION(<clause>): If you want to share only part of the table, you can specify a partition. For example, (column = 'value') See Specify table partitions to share and Use recipient properties to do partition filtering.
AS <alias>: An alternate table name, or Alias to make the table name more readable. The alias is the table name that the recipient sees and must use in queries. Recipients cannot use the actual table name if an alias is specified. Use the format <schema-name>.<table-name>.
WITH HISTORY or WITHOUT HISTORY: When WITH HISTORY is specified, share the table with full history, allowing recipients to perform time travel queries and streaming reads. For Databricks-to-Databricks shares, history sharing also shares the table’s Delta log to improve performance, see Improve table read performance with history sharing. The default behavior for table sharing is WITHOUT HISTORY and for schema sharing is WITH HISTORY. Requires Databricks Runtime 12.2 LTS or above.

Note

If, in addition to doing time travel queries and streaming reads, you want your customers to be able to query a table’s change data feed (CDF) using the table_changes() function, you must enable CDF on the table before you share it WITH HISTORY.

For more information about ALTER SHARE options, see ALTER SHARE.

To add a table, run the following command using the Databricks CLI.

databricks shares update <share-name> \
  --json '{
    "updates": [
      {
        "action": "ADD",
        "data_object": {
          "name": "<table-full-name>",
          "data_object_type": "TABLE",
          "shared_as": "<table-alias>"
        }
      }
    ]
  }'

To add a schema, run the following Databricks CLI command:

databricks shares update <share-name> \
  --json '{
    "updates": [
      {
        "action": "ADD",
        "data_object": {
          "name": "<schema-full-name>",
          "data_object_type": "SCHEMA"
        }
      }
    ]
  }'

Note

For tables, and only tables, you can omit "data_object_type".

To learn about the options listed in this example, view the instructions on the SQL tab.

To learn about additional parameters, run databricks shares update --help or see PATCH /api/2.1/unity-catalog/shares/ in the REST API reference.

For information about removing tables from a share, see Update shares.

Specify table partitions to share

To share only part of a table when you add the table to a share, you can provide a partition specification. You can specify partitions when you add a table to a share or update a share, using Catalog Explorer, the Databricks Unity Catalog CLI, or SQL commands in a Databricks notebook or the Databricks SQL query editor. See Add tables to a share and Update shares.

Basic example

The following SQL example shares part of the data in the inventory table, partitioned by the year, month, and date columns:

Data for the year 2021.
Data for December 2020.
Data for December 25, 2019.

ALTER SHARE share_name
ADD TABLE inventory
PARTITION (year = "2021"),
          (year = "2020", month = "Dec"),
          (year = "2019", month = "Dec", date = "2019-12-25");

Use recipient properties to do partition filtering

You can share a table partition that matches data recipient properties, also known as parameterized partition sharing.

Default properties include:

databricks.accountId: The Databricks account that a data recipient belongs to (Databricks-to-Databricks sharing only).
databricks.metastoreId: The Unity Catalog metastore that a data recipient belongs to (Databricks-to-Databricks sharing only).
databricks.name: The name of the data recipient.

You can create any custom property you like when you create or update a recipient.

Filtering by recipient property enables you to share the same tables, using the same share, across multiple Databricks accounts, workspaces, and users while maintaining data boundaries between them.

For example, if your tables include a Databricks account ID column, you can create a single share with table partitions defined by Databricks account ID. When you share, Delta Sharing dynamically delivers to each recipient only the data associated with their Databricks account.

Diagram of parameter-based dynamic partition sharing in Delta Sharing

Without the ability to dynamically partition by property, you would have to create a separate share for each recipient.

To specify a partition that filters by recipient properties when you create or update a share, you can use Catalog Explorer or the CURRENT_RECIPIENT SQL function in a Databricks notebook or the Databricks SQL query editor:

Note

Recipient properties are available on Databricks Runtime 12.2 and above.

In your Databricks workspace, click Catalog.
At the top of the Catalog pane, click the gear icon and select Delta Sharing.

Alternatively, from the Quick access page, click the Delta Sharing > button.
On the Shared by me tab, find the share you want to update and click its name.
Click Manage assets > Add data assets.
On the Add tables page, select the catalog and database that contain the table, then select the table.

If you aren’t sure which catalog and database contain the table, you can search for it by name, column name, or comment using workspace search. See Search for workspace objects.
(Optional) Click Advanced table options to add Partition specifications.

On the Add partition to a table dialog, add the property-based partition specification using the following syntax:
```
(<column-name> = CURRENT_RECIPIENT().<property-key>)
```
For example,
```
(country = CURRENT_RECIPIENT().'country')
```
Click Save.

Run the following command in a notebook or the Databricks SQL query editor:

ALTER SHARE <share-name> ADD TABLE <catalog-name>.<schema-name>.<table-name>
   PARTITION (<column-name> = CURRENT_RECIPIENT().<property-key>);

For example,

ALTER SHARE acme ADD TABLE acme.default.some_table
  PARTITION (country = CURRENT_RECIPIENT().'country');

Add views to a share

Preview

This feature is in Public Preview.

Views are read-only objects created from one or more tables or other views. A view can be created from tables and other views that are contained in multiple schemas and catalogs in a Unity Catalog metastore. See Create and manage views.

This section describes how to add views to a share using Catalog Explorer, Databricks CLI, or SQL commands in a Databricks notebook or the Databricks SQL query editor. If you prefer to use the Unity Catalog REST API, see PATCH /api/2.1/unity-catalog/shares/ in the REST API reference.

Permissions required: Owner of the share object, USE CATALOG and USE SCHEMA on the catalog and schema that contain the view, and SELECT on the view. You must maintain the SELECT privilege for as long as you want to share the view. For more information, see Requirements.

Additional requirements:

You must enable Serverless compute for workflows, notebooks, and Delta Live Tables in the account where view sharing is set up. See Enable serverless compute.
Shareable views must be defined on Delta tables or other shareable views.
You cannot share views that reference shared tables or shared views.
You must use a SQL warehouse or a cluster on Databricks Runtime 13.3 LTS or above when you add a view to a share.
For requirements and limitations on recipient usage of views, see Read shared views.

To add views to a share:

In your Databricks workspace, click Catalog.
At the top of the Catalog pane, click the gear icon and select Delta Sharing.

Alternatively, from the Quick access page, click the Delta Sharing > button.
On the Shared by me tab, find the share you want to add a view to and click its name.
Click Manage assets > Add data assets.
On the Add tables page, search or browse for the view that you want to share and select it.
(Optional) Click Advanced table options to specify an Alias, or alternate view name, to make the view name more readable. The alias is the name that the recipient sees and must use in queries. Recipients cannot use the actual view name if an alias is specified.
Click Save.

Run the following command in a notebook or the Databricks SQL query editor:

ALTER SHARE <share-name> ADD VIEW <catalog-name>.<schema-name>.<view-name>
   [COMMENT "<comment>"]
   [AS <alias>];

Options include:

AS <alias>: An alternate view name, or alias, to make the view name more readable. The alias is the view name that the recipient sees and must use in queries. Recipients cannot use the actual view name if an alias is specified. Use the format <schema-name>.<view-name>.
COMMENT "<comment>": Comments appear in the Catalog Explorer UI and when you list and display view details using SQL statements.

For more information about ALTER SHARE options, see ALTER SHARE.

Run the following Databricks CLI command:

databricks shares update <share-name> \
  --json '{
    "updates": [
      {
        "action": "ADD",
        "data_object": {
          "name": "<view-full-name>",
          "data_object_type": "VIEW",
          "shared_as": "<view-alias>"
        }
      }
    ]
  }'

"shared_as": "<view-alias>" is optional and provides an alternate view name, or alias, to make the view name more readable. The alias is the view name that the recipient sees and must use in queries. Recipients cannot use the actual view name if an alias is specified. Use the format <schema-name>.<view-name>.

To learn about additional parameters, run databricks shares update --help or see PATCH /api/2.1/unity-catalog/shares/ in the REST API reference.

For information about removing views from a share, see Update shares.

Add dynamic views to a share to filter rows and columns

Preview

This feature is in Public Preview.

You can use dynamic views to configure fine-grained access control to table data, including:

Security at the level of columns or rows.
Data masking.

When you create a dynamic view that uses the CURRENT_RECIPIENT() function, you can limit recipient access according to properties that you specify in the recipient definition.

This section provides examples of restricting recipient access to table data at both the row and column level using a dynamic view.

Requirements

Databricks Runtime version: The CURRENT_RECIPIENT function is supported in Databricks Runtime 14.2 and above.
Permissions:
- To create a view, you must be the owner of the share object, have USE CATALOG and USE SCHEMA on the catalog and schema that contain the view, along with SELECT on the view. You must maintain the SELECT privilege for as long as you want to share the view.
- To set properties on a recipient, you must be the owner of the recipient object.
Limitations: All limitations for view sharing, including restriction to Databricks-to-Databricks sharing, plus the following:
- When a provider shares a view that uses the CURRENT_RECIPIENT function, the provider can’t query the view directly because of the sharing context. To test such a dynamic view, the provider must share the view with themselves and query the view as a recipient.
- Providers cannot create a view that references a dynamic view.

Set a recipient property

In these examples, the table to be shared has a column named country, and only recipients with a matching country property can view certain rows or columns.

You can set recipient properties using Catalog Explorer or SQL commands in a Databricks notebook or the SQL query editor.

In your Databricks workspace, click Catalog.
At the top of the Catalog pane, click the gear icon and select Delta Sharing.

Alternatively, from the Quick access page, click the Delta Sharing > button.
On the Recipients tab, find the recipient you want to add the properties to and click its name.
Click Edit properties.
On the Edit recipient properties dialog, enter the column name as a key (in this case country) and the value you want to filter by as the value (for example, CA).
Click Save.

To set the property on the recipient, use ALTER RECIPIENT. In this example, the country property is set to CA.

ALTER RECIPIENT recipient1 SET PROPERTIES ('country' = 'CA');

Create a dynamic view with row-level permission for recipients

In this example, only recipients with a matching country property can view certain rows.

CREATE VIEW my_catalog.default.view1 AS
  SELECT * FROM my_catalog.default.my_table
  WHERE country = CURRENT_RECIPIENT('country');

Another option is for the data provider to maintain a separate mapping table that maps fact table fields to recipient properties, allowing recipient properties and fact table fields to be decoupled for greater flexiblity.

Create a dynamic view with column-level permission for recipients

In this example, only recipients that match the country property can view certain columns. Others see the data returned as REDACTED:

CREATE VIEW my_catalog.default.view2 AS
  SELECT
  CASE
    WHEN CURRENT_RECIPIENT('country') = 'US' THEN pii
    ELSE 'REDACTED'
  END AS pii
  FROM my_catalog.default.my_table;

Add volumes to a share

Volumes are Unity Catalog objects that represent a logical volume of storage in a cloud object storage location. They are intended primarily to provide governance over non-tabular data assets. See What are Unity Catalog volumes?.

This section describes how to add volumes to a share using Catalog Explorer, the Databricks CLI, or SQL commands in a Databricks notebook or SQL query editor. If you prefer to use the Unity Catalog REST API, see PATCH /api/2.1/unity-catalog/shares/ in the REST API reference.

Note

Volume comments are included in shares that are shared with a recipient using Databricks-to-Databricks sharing on or after July 25, 2024. If you want to start sharing comments through a share that was shared with a recipient before the release date, you must revoke and re-grant recipient access to trigger comment sharing.

Permissions required: Owner of the share object, USE CATALOG and USE SCHEMA on the catalog and schema that contain the volume, and READ VOLUME on the volume. You must maintain the READ VOLUME privilege for as long as you want to share the volume. For more information, see Requirements.

Additional requirements:

Volume sharing is supported only in Databricks-to-Databricks sharing.
You must use a SQL warehouse on version 2023.50 or above or a cluster on Databricks Runtime 14.1 or above when you add a volume to a share.
If the volume storage on the provider side has custom network configurations (such as a firewall or private link), then the provider must ensure that the recipient’s control plane and data plane addresses are properly allowlisted to be able to connect to the storage location of the volume.

To add volumes to a share:

In your Databricks workspace, click Catalog.
At the top of the Catalog pane, click the gear icon and select Delta Sharing.

Alternatively, from the Quick access page, click the Delta Sharing > button.
On the Shared by me tab, find the share you want to add a volume to and click its name.
Click Manage assets > Edit assets.
On the Edit assets page, search or browse for the volume that you want to share and select it.

Alternatively, you can select the entire schema that contains the volume. See Add schemas to a share.
(Optional) Click Advanced options to specify an alternate volume name, or Alias, to make the volume name more readable.

Aliases are not available if you select an entire schema.

The alias is the name that the recipient sees and must use in queries. Recipients cannot use the actual volume name if an alias is specified.
Click Save.

Run the following command in a notebook or the Databricks SQL query editor:

ALTER SHARE <share-name> ADD VOLUME <catalog-name>.<schema-name>.<volume-name>
   [COMMENT "<comment>"]
   [AS <alias>];

Options include:

AS <alias>: An alternate volume name, or alias, to make the volume name more readable. The alias is the volume name that the recipient sees and must use in queries. Recipients cannot use the actual volume name if an alias is specified. Use the format <schema-name>.<volume-name>.
COMMENT "<comment>": Comments appear in the Catalog Explorer UI and when you list and display volume details using SQL statements.

For more information about ALTER SHARE options, see ALTER SHARE.

Run the following command using Databricks CLI 0.210 or above:

 databricks shares update <share-name> \
   --json '{
     "updates": [
       {
         "action": "ADD",
         "data_object": {
           "name": "<volume-full-name>",
           "data_object_type": "VOLUME",
           "string_shared_as": "<volume-alias>"
         }
       }
     ]
   }'

"string_shared_as": "<volume-alias>" is optional and provides an alternate volume name, or alias, to make the volume name more readable. The alias is the volume name that the recipient sees and must use in queries. Recipients cannot use the actual volume name if an alias is specified. Use the format <schema-name>.<volume-name>.

To learn about additional parameters, run databricks shares update --help or see PATCH /api/2.1/unity-catalog/shares/ in the REST API reference.

For information about removing volumes from a share, see Update shares.

Add models to a share

This section describes how to add models to a share using Catalog Explorer, the Databricks CLI, or SQL commands in a Databricks notebook or SQL query editor. If you prefer to use the Unity Catalog REST API, see PATCH /api/2.1/unity-catalog/shares/ in the REST API reference.

Note

Model comments and model version comments are included in shares that are shared using Databricks-to-Databricks sharing.

Permissions required: Owner of the share object, USE CATALOG and USE SCHEMA on the catalog and schema that contain the model, and EXECUTE on the model. You must maintain the EXECUTE privilege for as long as you want to share the model. For more information, see Requirements.

Additional requirements:

Model sharing is supported only in Databricks-to-Databricks sharing.
You must use a SQL warehouse on version 2023.50 or above or a cluster on Databricks Runtime 14.0 or above when you add a model to a share.

To add models to a share:

In your Databricks workspace, click Catalog.
At the top of the Catalog pane, click the gear icon and select Delta Sharing.

Alternatively, from the Quick access page, click the Delta Sharing > button.
On the Shared by me tab, find the share you want to add a model to and click its name.
Click Manage assets > Edit assets.
On the Edit assets page, search or browse for the model that you want to share and select it.

Alternatively, you can select the entire schema that contains the model. See Add schemas to a share.
(Optional) Click Advanced options to specify an alternate model name, or Alias, to make the model name more readable.

Aliases are not available if you select an entire schema.

The alias is the name that the recipient sees and must use in queries. Recipients cannot use the actual model name if an alias is specified.
Click Save.

Run the following command in a notebook or the Databricks SQL query editor:

ALTER SHARE <share-name> ADD MODEL <catalog-name>.<schema-name>.<model-name>
   [COMMENT "<comment>"]
   [AS <alias>];

Options include:

AS <alias>: An alternate model name, or alias, to make the model name more readable. The alias is the model name that the recipient sees and must use in queries. Recipients cannot use the actual model name if an alias is specified. Use the format <schema-name>.<model-name>.
COMMENT "<comment>": Comments appear in the Catalog Explorer UI and when you list and display model details using SQL statements.

For more information about ALTER SHARE options, see ALTER SHARE.

Run the following command using Databricks CLI 0.210 or above:

 databricks shares update <share-name> \
   --json '{
     "updates": [
       {
         "action": "ADD",
         "data_object": {
           "name": "<model-full-name>",
           "data_object_type": "MODEL",
           "string_shared_as": "<model-alias>"
         }
       }
     ]
   }'

"string_shared_as": "<model-alias>" is optional and provides an alternate model name, or alias, to make the model name more readable. The alias is the model name that the recipient sees and must use in queries. Recipients cannot use the actual model name if an alias is specified. Use the format <schema-name>.<model-name>.

To learn about additional parameters, run databricks shares update --help or see PATCH /api/2.1/unity-catalog/shares/ in the REST API reference.

For information about removing models from a share, see Update shares.

Update shares

In addition to adding tables, views, volumes, and notebooks to a share, you can:

Rename a share.
Remove tables, views, volumes, and schemas from a share.
Add or update a comment on a share.
Enable or disable access to a table’s history data, allowing recipients to perform time travel queries or streaming reads of the table.
Add, update, or remove partition definitions.
Change the share owner.

To make these updates to shares, you can use Catalog Explorer, the Databricks Unity Catalog CLI, or SQL commands in a Databricks notebook or the Databricks SQL query editor. You cannot use Catalog Explorer to rename the share.

Permissions required: To update the share owner, you must be one of the following: a metastore admin, the owner of the share object, or a user with both the USE SHARE and SET SHARE PERMISSION privileges. To update the share name, you must be a metastore admin (or user with the CREATE_SHARE privilege) and share owner. To update any other share properties, you must be the owner.

In your Databricks workspace, click Catalog.
At the top of the Catalog pane, click the gear icon and select Delta Sharing.

Alternatively, from the Quick access page, click the Delta Sharing > button.
On the Shared by me tab, find the share you want to update and click its name.

On the share details page, do the following:

Click the edit icon next to the Owner or Comment field to update these values.
Click the kebab menu button in an asset row to remove it.
Click Manage assets > Edit assets to update all other properties:
- To remove an asset, clear the checkbox next to the asset.
- To add, update, or remove partition definitions, click Advanced options.

Run the following commands in a notebook or the Databricks SQL editor.

Rename a share:

ALTER SHARE <share-name> RENAME TO <new-share-name>;

Remove tables from a share:

ALTER SHARE share_name REMOVE TABLE <table-name>;

Remove volumes from a share:

ALTER SHARE share_name REMOVE VOLUME <volume-name>;

Add or update a comment on a share:

COMMENT ON SHARE <share-name> IS '<comment>';

Add or modify partitions for a table in a share:

ALTER SHARE <share-name> ADD TABLE <table-name> PARTITION(<clause>);

Change share owner:

ALTER SHARE <share-name> OWNER TO  '<principal>'

-- Principal must be an account-level user email address or group name.

Enable history sharing for a table:

ALTER SHARE <share-name> ADD TABLE <table-name> WITH HISTORY;

For details about ALTER SHARE parameters, see ALTER SHARE.

Run the following commands using the Databricks CLI.

Rename a share:

databricks shares update <share-name> --name <new-share-name>

Remove tables from a share:

databricks shares update <share-name> \
  --json '{
    "updates": [
      {
        "action": "REMOVE",
        "data_object": {
          "name": "<table-full-name>",
          "data_object_type": "TABLE",
          "shared_as": "<table-alias>"
        }
      }
    ]
  }'

Remove volumes from a share (using Databricks CLI 0.210 or above):

databricks shares update <share-name> \
  --json '{
    "updates": [
      {
        "action": "REMOVE",
        "data_object": {
          "name": "<volume-full-name>",
          "data_object_type": "VOLUME",
          "string_shared_as": "<volume-alias>"
        }
      }
    ]
  }'

Note

Use the name property if there is no alias for the volume. Use string_shared_as if there is an alias.

Add or update a comment on a share:

databricks shares update <share-name> --comment '<comment>'

Change share owner:

databricks  shares update <share-name> --owner '<principal>'

Principal must be an account-level user email address or group name.

Create and manage shares for Delta Sharing

Requirements

Create a share object

Add tables to a share

Specify table partitions to share

Basic example

Use recipient properties to do partition filtering

Add tables with deletion vectors or column mapping to a share

Add views to a share

Add dynamic views to a share to filter rows and columns

Requirements

Set a recipient property

Create a dynamic view with row-level permission for recipients

Create a dynamic view with column-level permission for recipients

Share the dynamic view with a recipient

Add volumes to a share

Add models to a share

Add schemas to a share

Add notebook files to a share

Remove notebook files from shares

Update notebook files in shares

Grant recipients access to a share

View shares and share details

View the recipients who have permissions on a share

Update shares

Delete a share