databricks

Overview ¶

Example: lake-orm against a Databricks SQL warehouse using the native `databricks-sql-go` driver. Bring-your-own-connection — lake-orm doesn't own OAuth, warehouse selection, or connection pooling; you construct the *sql.DB exactly as your environment requires and hand it to driver/databricks.

Required env:

DATABRICKS_WORKSPACE_HOST   e.g. "acme.cloud.databricks.com"
DATABRICKS_WAREHOUSE_ID     e.g. "0123456789abcdef"
DATABRICKS_CLIENT_ID        OAuth M2M client ID (service principal)
DATABRICKS_CLIENT_SECRET    OAuth M2M client secret
DATABRICKS_CATALOG          e.g. "main"
DATABRICKS_SCHEMA           e.g. "analytics"

Authentication, session config, and connection-pool sizing are Databricks-specific knobs that every deployment tunes differently. The reference implementation in svc-data-platform-api/internal/datalake documents the set that works at production scale; this example is the minimum viable wiring.