> For the complete documentation index, see [llms.txt](https://help.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.felt.com/data-sources/cloud-sources/databricks.md).

# Databricks

{% embed url="<https://youtu.be/nfL94qQG8HA?si=Jny1SdQ7bKm2E0Yw>" %}

Connect to [Databricks](https://www.databricks.com/) to analyze and visualize your data lake insights directly in Felt.

{% hint style="success" %}
This feature is only available to customers on the [Enterprise plan](https://felt.com/pricing). To upgrade, [contact sales](https://felt.com/sales).
{% endhint %}

1. Create a new, read-only user on your database for Felt access
2. Open **New data source** — from the workspace homepage, click **+** next to **Data sources**. Or from a map, click ![](/files/qv8POfyKJ00VfTgugMR2) in the toolbar and choose **+ New data source**.
3. Select **Databricks**
4. Enter Connection Details
   1. **Source Name**: name of the source in Felt
   2. **Host**: The server hostname of the cluster or SQL warehouse. You can get this from the **Server Hostname** value in the [**Advanced Options > JDBC/ODBC**](https://docs.databricks.com/en/integrations/compute-details.html) tab for your cluster.
   3. **HTTP Path**: The HTTP path of the cluster or SQL warehouse. You can get this from the **HTTP Path** value in the [**Advanced Options > JDBC/ODBC**](https://docs.databricks.com/en/integrations/compute-details.html) tab for your cluster.
   4. **Catalog**: (optional) the name of the catalog to read.
   5. **Schema**: (optional) the name of the database schema to read. If not provided, all schemas from the database will be read.
5. Enter credential information
   1. Select a credential type
      1. **Databricks PAT**. See Databricks' [documentation for Personal Access Tokens](https://docs.databricks.com/aws/en/dev-tools/auth/pat)
         1. Generate a token
         2. Fill in the **Personal Access Token** field with it
      2. **M2M OAuth**. See Databricks' [documentation for M2M OAuth](https://docs.databricks.com/aws/en/dev-tools/auth/oauth-m2m). To grant Felt access using M2M OAuth you must:
         1. Create a Service Principal in your account or workspace and copy the `client_id` and `client_secret`
         2. Navigate to the Databricks workspace that you want to grant Felt access to
         3. Navigate to the `Catalog` tab
         4. Select the Catalog
         5. Navigate to the `Permissions` tab
         6. Click `Grant`
         7. Select the Service Principal you've created for Felt
         8. Grant the `SELECT` , `BROWSE`, `USE_CATALOG`, and `USE_SCHEMA` permissions
         9. Fill in the **Client ID** and **Client Secret** fields
6. Click **Connect**
7. Once connected you will see a catalog of your data with previews for your new source
8. From here you can add any of these layers to your maps!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.felt.com/data-sources/cloud-sources/databricks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.