Integrations / Databricks
Databricks
Databricks is a unified analytics platform for big data and AI
What Telara does
Capability matrix
Before you connect
Prerequisites
Vendor setup
Get the credential
Permissions Telara requests
- all-apisOAuth 2.0
- offline_accessOAuth 2.0
- all-apisOAuth 2.0
In Telara
Connect in Telara
Workspace OAuth user-to-machine authorization-code flow. Requires a validated Databricks workspace host and a registered OAuth app before browser authorization can be enabled.
In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.
Workspace OAuth client-credentials flow for a Databricks service principal. Requires a validated workspace host and service-principal OAuth client credentials.
In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.
In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.
- Host
- Access token
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Notebook | Partial — not every record the vendor holds is synced |
| Job | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Notebook | Up to 1 day | Removed records disappear on the next full sync |
| Job | Up to 1 day | Removed records disappear on the next full sync |
Data handling
Permissions & data handling
The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.
Excluded from semantic search: Notebook, Job.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty