Integration
Databricks
Unified analytics platform
- Category
- Data warehouses
- Runs in
- The Phloem cloud — nothing to install
Lets you and Hamming query a Unity Catalog through a Databricks SQL warehouse, with its tables listed in Trace.
What Phloem reads
- Tables in every schema of the catalog — columns, types, and comments and row counts where the table has them — listed in Trace for Hamming and SQL autocomplete
information_schemais left out
What you need
- Your workspace hostname and the SQL warehouse's HTTP Path (from its Connection Details)
- A personal access token, or a service principal's client ID and secret for OAuth
- The Unity Catalog to read
Connect
- In the console, open Connectors, choose Add connector, then Databricks.
- Under Authentication Method, choose API Key or OAuth (Service Principal).
- Enter Host and HTTP Path.
- In Access Token, enter the personal access token, or for OAuth the client secret plus Client ID.
- Enter Catalog, and optionally a default Schema.
- Choose Test Connection, then Create Connection.
What Hamming can do
- Run SQL that you or Hamming write, on the warehouse at that HTTP Path
Notes
- Catalog is optional on the form, but without it nothing is listed in Trace.
- A stopped warehouse can make the first test time out while it starts. Test again once it runs.
- Phloem runs any statement, not only
SELECT. Use a token or service principal with read-only grants to keep the connector read-only.
#Connection fields
What the Add connector form asks for.
| Field | Type | Required |
|---|---|---|
| Host Databricks workspace URL adb-1234567890123456.7.azuredatabricks.net | Text | Yes |
| HTTP Path SQL Warehouse HTTP path from Connection Details /sql/1.0/warehouses/abc123def456 | Text | Yes |
| Access Token Personal Access Token (for API Key) or Client Secret (for OAuth) | Secret | Yes |
| Client ID Service Principal Client ID (for OAuth only) your-client-id | Text | — |
| Catalog Unity Catalog name (optional) main | Text | — |
| Schema Default schema default | Text | — |
Updated