Databricks
Connect a Databricks SQL warehouse to Lakehousecat using a connection URI.
Availability
This datasource type is being rolled out and is not yet selectable when you create a datasource. This page describes the intended connection method.
Connection Fields
| Field | Required | Description |
|---|---|---|
| Connection URI | Yes | Connection string with personal access token and HTTP path. Example: databricks://token:dapi...@host.azuredatabricks.net/default?http_path=/sql/1.0/warehouses/abc123 |
| Use SSH | No | Enable to connect through an SSH bastion host. |
Prerequisites
- Admin or Builder role in Lakehousecat
- A Databricks personal access token with access to the target SQL warehouse
- The HTTP path of the SQL warehouse (found under SQL Warehouses → Connection details in the Databricks UI)
- Network connectivity from the Lakehousecat backend to the Databricks workspace
Notes
- Use the HTTP path of a SQL warehouse, not a cluster, for best performance and reliability.
- The
defaultcatalog in the URI can be replaced with any Unity Catalog catalog name. - Incremental Load is supported; use a timestamp column (e.g.,
updated_at) as the merge key.
Next Steps
After creating the datasource, go to the Operations tab to trigger semantic extraction.