How Ridge works with Delta Lake
Ridge AI's Databricks connector gives you direct access to your Unity Catalog tables. PointRidge at a table or write a SQL query, and Ridge ingests the results into its analytics engine ona schedule — ready to power a dashboard and Data Agent.
What you can do
- Connect to Unity Catalog and read Delta Lake tables
- Reference a table directly, or shape it with custom SQL
- Filter and aggregate at the source with WHERE and GROUP BY
- Refresh on a schedule with standard cron expressions
What you'll need
Four pieces of information connect Ridge to your workspace. Collect these from Databricks before you start — the whole setup takes about five minutes.
Set up the connection
1 Create a Connection
On the Data page, click New Connection and choose Databricks as the type. Enter the fourcredentials you gathered, then save.
- Token — your Databricks access token
- Endpoint — your workspace URL
- AWS Region — your workspace region
- Catalog — the Unity Catalog name
2 Create a Dataset
Back on the Data page, click New, select source Connection, and pick the Databricks connection you just created. A Data Set points at a specific table and can carry its own query and refresh schedule.
3 Select a table, or write a query
Choose how Ridge reads from the catalog. A direct table reference is simplest; custom SQL lets you filter and aggregate at the source.
Option A — Table reference
SELECT
customer_id,
SUM(amount) AS total_amount
FROM main.sales.transactions
WHERE year = 2024
GROUP BY customer_id
Option B — Custom SQL
SELECT
customer_id,
SUM(amount) AS total_amount
FROM main.sales.transactions
WHERE year = 2024
GROUP BY customer_id
4 Schedule ingestion
Set an ingestion schedule with standard cron syntax, then save. Ridge runs your query againstUnity Catalog and stores the results, ready for analysis.
What happens on each run
- Ridge executes your query against Databricks Unity Catalog
- Results are exported to Parquet format
- Data is stored in Ridge's object storage (R2)
- The Data Set becomes available for visualization and the Data Agent
Best practices
A few habits keep ingestion fast, secure, and predictable.
Supported features & limitations
Troubleshooting
Most connection issues fall into four buckets. Expand the one that matches your error.
Invalid credentials
401, "invalid access token", "unauthorized", "Invalid token", "Authentication failed"
Your token is wrong or expired. Rotate or re-enter it, and check that you copied the token completely with no extra spaces. For service principals, confirm the principal has catalog access.
Insufficient permissions
403, "permission denied"
The token lacks rights on the catalog. Grant the principal access to the catalog or schema.
Resource not found
404, "resource does not exist", "catalog '…'"
The catalog or table name is wrong. Fix the catalog or table identifier.
Network unreachable
"could not resolve host", "timed out", "connection refused"
The endpoint is unreachable or egress is blocked. Check the endpoint URL and any egress allowlist.
.avif)