You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/resources/provider.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,11 @@
1
1
---
2
-
subcategory: "Unity Catalog"
2
+
subcategory: "Delta Sharing"
3
3
---
4
4
# databricks_provider Resource
5
5
6
6
-> **Note** This resource could be only used with workspace-level provider!
7
7
8
-
Within a metastore, Unity Catalog provides the ability to create a provider which contains a list of shares that have been shared with you.
8
+
In Delta Sharing, a provider is an entity that shares data with a recipient. Within a metastore, Unity Catalog provides the ability to create a provider which contains a list of shares that have been shared with you.
9
9
10
10
A `databricks_provider` is contained within [databricks_metastore](metastore.md) and can contain a list of shares that have been shared with you.
Copy file name to clipboardExpand all lines: docs/resources/recipient.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,13 @@
1
1
---
2
-
subcategory: "Unity Catalog"
2
+
subcategory: "Delta Sharing"
3
3
---
4
4
# databricks_recipient Resource
5
5
6
6
-> **Note** This resource could be only used with workspace-level provider!
7
7
8
-
Within a metastore, Unity Catalog provides the ability to create a recipient to attach delta shares to.
8
+
In Delta Sharing, a recipient is an entity that receives shares from a provider. In Unity Catalog, a share is a securable object that represents an organization and associates it with a credential or secure sharing identifier that allows that organization to access one or more shares.
9
+
10
+
As a data provider (sharer), you can define multiple recipients for any given Unity Catalog metastore, but if you want to share data from multiple metastores with a particular user or group of users, you must define the recipient separately for each metastore. A recipient can have access to multiple shares.
9
11
10
12
A `databricks_recipient` is contained within [databricks_metastore](metastore.md) and can have permissions to `SELECT` from a list of shares.
11
13
@@ -113,7 +115,6 @@ In addition to all arguments above, the following attributes are exported:
113
115
*`cloud` - Cloud vendor of the recipient's Unity Catalog Metstore. This field is only present when the authentication_type is `DATABRICKS`.
114
116
*`region` - Cloud region of the recipient's Unity Catalog Metstore. This field is only present when the authentication_type is `DATABRICKS`.
115
117
116
-
117
118
## Related Resources
118
119
119
120
The following resources are often used in the same context:
Copy file name to clipboardExpand all lines: docs/resources/share.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,13 @@
1
1
---
2
-
subcategory: "Unity Catalog"
2
+
subcategory: "Delta Sharing"
3
3
---
4
4
# databricks_share Resource
5
5
6
6
-> **Note** This resource could be only used with workspace-level provider!
7
7
8
-
Within a metastore, Unity Catalog provides the ability to create a share, which is a named object that contains a collection of tables in a metastore that you want to share as a group. A share can contain tables from only a single metastore. You can add or remove tables from a share at any time.
8
+
In Delta Sharing, a share is a read-only collection of tables and table partitions that a provider wants to share with one or more recipients. If your recipient uses a Unity Catalog-enabled Databricks workspace, you can also include notebook files, views (including dynamic views that restrict access at the row and column level), Unity Catalog volumes, and Unity Catalog models in a share.
9
9
10
-
A `databricks_share` is contained within [databricks_metastore](metastore.md) and can contain a list of tables.
10
+
In a Unity Catalog-enabled Databricks workspace, a share is a securable object registered in Unity Catalog. A `databricks_share` is contained within a [databricks_metastore](metastore.md). If you remove a share from your Unity Catalog metastore, all recipients of that share lose the ability to access it.
0 commit comments