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: src/unify/linked-profiles/setup-guides/databricks-setup.md
+4-5Lines changed: 4 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,14 +8,14 @@ hidden: true
8
8
> info "Linked Events is in private beta"
9
9
> Linked Events is in private beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available.
10
10
11
-
On this page, you'll learn how to connect your Databricks data warehouse to Segment.
11
+
On this page, you'll learn how to connect your Databricks data warehouse to your Segment Data Graph.
12
12
13
13
> info ""
14
14
> At this time, you can only use Databricks with Linked Audiences.
15
15
16
16
## Set up Databricks credentials
17
17
18
-
Sign into Databricks with admin permissions to provide Segment's Data Graph with the necessary permissions.
18
+
Sign into Databricks with admin permissions to create new resources and provide Data Graph with the necessary permissions.
19
19
20
20
Segment assumes that you already have a workspace that includes the datasets you'd like to use for the Data Graph. Segment recommends setting up a new Service Principal user with only the permissions to access the required catalogs and schemas.
21
21
@@ -120,7 +120,7 @@ GRANT SELECT ON TABLE `${table_2}` TO `${client_id}`;
120
120
121
121
### Step 5: Validate the permissions of your Service Principal user
122
122
123
-
Sign into the Databricks CLI with your Client ID secret and run the following SQL to verify the Service Principal user has the correct permissions for a given table.
123
+
Sign into the [Databricks CLI with your Client ID secret](https://docs.databricks.com/en/dev-tools/cli/authentication.html#oauth-machine-to-machine-m2m-authentication){:target="_blank”} and run the following SQL to verify the Service Principal user has the correct permissions for a given table.
124
124
125
125
> success ""
126
126
> If this command succeeds, you can view the table.
@@ -154,5 +154,4 @@ If Segment Reverse ETL has ever run in the catalog you are configuring as the Se
154
154
155
155
```sql
156
156
GRANT ALL PRIVILEGES ON SCHEMA ${segment_internal_catalog}.__segment_reverse_etl TO `${client_id}`;
0 commit comments