Skip to content

Commit 60e2f67

Browse files
committed
[netlify-build]
1 parent e077f5c commit 60e2f67

File tree

2 files changed

+9
-1
lines changed

2 files changed

+9
-1
lines changed

src/connections/reverse-etl/reverse-etl-source-setup-guides/databricks-setup.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,16 @@
22
title: Databricks Reverse ETL Setup
33
---
44

5+
> info ""
6+
> The Databricks Reverse ETL source is in beta and Segment is actively working on this feature. Segment's [First-Access and Beta terms](https://segment.com/legal/first-access-beta-preview/) govern this feature.
7+
58
Set up Databricks as your Reverse ETL source.
69

710
At a high level, when you set up Databricks for Reverse ETL, the configured user needs read permissions for any resources (databases, schemas, tables) the query needs to access. Segment keeps track of changes to your query results with a managed schema (`__SEGMENT_REVERSE_ETL`), which requires the configured user to allow write permissions for that schema.
811

912
## Required permissions
13+
* Make sure the user or the service principal you use to connect to Segment has permissions to use that warehouse. In the Databricks console go to **SQL warehouses** and select the warehouse you're using. Navigate to **Overview > Permissions** and make sure the user or the service principal you use to connect to Segment has *can use* permissions.
14+
1015
* To grant access to read data from the tables used in the model query, run:
1116

1217
```

src/connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,9 @@
22
title: Postgres Reverse ETL Setup
33
---
44

5+
> info ""
6+
> The Postgres Reverse ETL source is in beta and Segment is actively working on this feature. Segment's [First-Access and Beta terms](https://segment.com/legal/first-access-beta-preview/) govern this feature.
7+
58
Set up Postgres as your Reverse ETL source.
69

710
At a high level, when you set up Postgres for Reverse ETL, the configured user/role needs read permissions for any resources (databases, schemas, tables) the query needs to access. Segment keeps track of changes to your query results with a managed schema (`__SEGMENT_REVERSE_ETL`), which requires the configured user to allow write permissions for that schema.
@@ -28,4 +31,4 @@ To set up Postgres with Reverse ETL:
2831
## Extra permissions
2932
* Give the `segment` user read permissions for any resources (databases, schemas, tables) the query needs to access.
3033

31-
* Give the `segment` user write permissions for the Segment managed schema (`__SEGMENT_REVERSE_ETL`), which keeps track of changes to the query results.
34+
* Give the `segment` user write permissions for the Segment managed schema (`__SEGMENT_REVERSE_ETL`), which keeps track of changes to the query results.

0 commit comments

Comments
 (0)