Databricks
The Databricks connector reads Unity Catalog metadata from one workspace over the Databricks REST API, authenticated with a personal access token. It is metadata-only by construction: the Unity Catalog endpoints it calls cannot return table rows, so there is no path by which it could read your data.
Connection settingsDirect link to Connection settings
| Field | Required | Notes |
|---|---|---|
workspaceHost | Yes | Your workspace hostname, without scheme or path (for example dbc-a1b2c3d4-e5f6.cloud.databricks.com). It must sit under one of the Databricks vendor domains — .cloud.databricks.com, .azuredatabricks.net, or .gcp.databricks.com. Any other host is refused. |
catalog | Yes | The Unity Catalog catalog to discover — one catalog per connector. |
personalAccessToken | Yes | A workspace personal access token. Stored in Supabase Vault; decrypted only in the sync worker and never shown again after saving. |
Testing the connection fetches the configured catalog by name — one idempotent metadata read that proves the token authenticates and the catalog is visible to it.
What gets discoveredDirect link to What gets discovered
- The configured catalog, as the catalog database.
- Unity Catalog schemas, as schemas (
information_schemais skipped). - Tables, with their columns embedded in the same listing — data type and nullability per column.
- Comments are first-class in Unity Catalog: table and column comments are captured into the catalog.
After a passed test, pick the schemas and tables to sync in the scope picker — see the connectors overview.
Network and egressDirect link to Network and egress
Egress is limited to your workspace host under the closed vendor-domain list above, and only to Unity Catalog metadata paths; names you configure travel as URL-encoded parameters, never as request paths. The resolved workspace address must also pass Metatate's private-address refusal, and all traffic runs over HTTPS with certificate verification against the workspace hostname.