jdbc:databricks://
No
Yes Yes Yes No Yes Yes Yes No Yes Yes| Field | Description |
|---|---|
| Data source | Databricks |
| Supported versions | 3.4.2 |
| Connection string | jdbc:databricks:// |
| Packaged? | No |
| Certified? | Yes |
| Supported features | |
| Estimate job | Yes |
| Analyze data | Yes |
| Schedule | No |
| Processing capabilities | |
| Pushdown | Yes |
| Spark agent | Yes |
| Yarn agent | Yes |
| Parallel JDBC | No |
| Java Platform version compatibility | |
| JDK 8 | Yes |
| JDK 11 | Yes |
| Field | Description |
|---|---|
| Data source | Databricks |
| Supported versions | 21.0.8137.0 |
| Connection string | jdbc:cdata:Databricks: |
| Packaged? | Yes |
| Certified? | Yes |
| Supported features | |
| Estimate job | Yes |
| Analyze data | Yes |
| Schedule | No |
| Processing capabilities | |
| Pushdown | Yes |
| Spark agent | Yes |
| Yarn agent | Yes |
| Parallel JDBC | Yes |
| Java Platform version compatibility | |
| JDK 8 | Yes |
| JDK 11 | Yes |
Yes | Name | Text | The unique name of your connection. Ensure that there are no spaces in your connection name. |
| Yes | Connection URL | String | The connection string path of your Databricks connection.
:glasses-round: Example: jdbc:databricks\://${host}:${port}/default;transportMode=http;ssl=1;HttpPath=${clusterHttpPath};AuthMech=3;UID=${username};PWD=${token}
Use the following format when connecting to Databricks SQL Warehouse:
jdbc:databricks\://\[Host]:\[Port]/\[Schema];\[Property1]=\[Value]; \[Property2]=\[Value];...
When referring to the example below, replace the ${value} sections of the connection URL with your actual value.
:glasses-round: Example: jdbc:databricks\://\
Use the following format when connecting to Databricks Compute:
jdbc:databricks\://\[Host]:\[Port]/\[Schema];\[Property1]=\[Value]; \[Property2]=\[Value];...
When referring to the example below, replace the ${value} sections of the connection URL with your actual value.
:glasses-round: Example: jdbc:databricks\://\
Use the following format when connecting to Databricks Unity Catalog:
jdbc:databricks\://\[Host]:\[Port]/\[Schema];\[Property1]=\[Value]; \[Property2]=\[Value];...ConnCatalog=catalog\_name
When referring to the example below, replace the ${value} sections of the connection URL with your actual value.
:glasses-round: Example: jdbc:databricks\://${host}:${port}/${Schema};transportMode=http;ssl=1;AuthMech=3;HttpPath=${clusterHttpPath};UID=token;PWD=${access\_token};ConnCatalog=${catalog}
Specify ${access\_token} on the Properties tab where Property Name is set to access\_token and Value is the password. This is so Collibra DQ treats the password as a sensitive property and does not display its actual value in the connection URL.
When referring to the example below, replace the ${value} sections of the connection URL with your actual value.
If you do not specify ConnCatalog=${catalog} in the JDBC connection URL, a default catalog is not set. Instead, you must include the catalog name in the query, as shown in the following example.select \* from catalog.schema.tableWhen you specify a catalog in the connection URL, you do not need to explicitly reference it when you query schema and data in the catalog, as shown in the following example.select \* from schema.table
Yes | Driver Name | String | The driver class name of your Databricks connection.
com.databricks.client.jdbc.Driver
Yes | Port | Integer | The port number to establish a connection to the datasource.
The default port is 0
No | Limit Schemas | Option | Allows you to manage usage and restrict visibility to only the necessary schemas in the Explorer tree.
See Limiting schemas to learn how to limit schemas from the Connection Management page.
When you include a restricted schema in the query of a DQ Job, the query scope may be overwritten when the job runs. While only the schemas you selected when you set up the connection are shown in the Explorer menu, users are not restricted from running SQL queries on any schema from the data source.
No | Source Name | String | N/A |
| No | Target Agent | Option | The [Agent](/data-quality-self-hosted/installation/agent.md) that submits your Spark job for processing. |
| Yes | Auth Type | Option | The method to authenticate your connection.
The configuration requirements are different depending on the Auth Type you select. See Authentication for more details on available authentication types.
No | Properties | String | The configurable driver properties for your connection. Multiple properties must be semicolon-delimited, and each property=value pair, including the last one, must end with a semicolon (;). `abc=123;test=true;` |
| No | Variables | String | When you specify ${access\_token} in the Connection URL, set the following properties on the Variables tab.
Variable Name is set to access\_token.
Value is the password.
| | No | [Archive Break Records](/data-quality-self-hosted/core-concepts/findings/break-records-and-link-ids/archiving-break-records-from-pushdown-jobs.md) | Option | Allows you to write break records directly to a Databricks database or schema.
Ensure that you have the necessary privileges to write break records to Databricks.
Yes | Name | Text | The unique name of your connection. Ensure that there are no spaces in your connection name. |
| Yes | Connection URL | String | The connection string path of your Databricks connection.
:glasses-round: Example: jdbc:cdata:Databricks:Server=https\://${server}.cloud.databricks.com;httpPath=${path};User=token;Token=${token};
Use the following format when connecting to Databricks SQL Warehouse:
jdbc:databricks\://\[Host]:\[Port]/\[Schema];\[Property1]=\[Value]; \[Property2]=\[Value];...
When referring to the example below, replace the ${value} sections of the connection URL with your actual value.
:glasses-round: Example: jdbc:databricks\://\
Use the following format when connecting to Databricks Compute:
jdbc:databricks\://\[Host]:\[Port]/\[Schema];\[Property1]=\[Value]; \[Property2]=\[Value];...
When referring to the example below, replace the ${value} sections of the connection URL with your actual value.
:glasses-round: Example: jdbc:databricks\://\
Use the following format when connecting to Databricks Unity Catalog:
jdbc:databricks\://\[Host]:\[Port]/\[Schema];\[Property1]=\[Value]; \[Property2]=\[Value];...ConnCatalog=catalog\_name
When referring to the example below, replace the ${value} sections of the connection URL with your actual value.
:glasses-round: Example: jdbc:databricks\://${host}:${port}/${Schema};transportMode=http;ssl=1;AuthMech=3;HttpPath=${clusterHttpPath};UID=token;PWD=${access\_token};ConnCatalog=${catalog}
Specify ${access\_token} on the Properties tab where Property Name is set to access\_token and Value is the password. This is so Collibra DQ treats the password as a sensitive property and does not display its actual value in the connection URL.
When referring to the example below, replace the ${value} sections of the connection URL with your actual value.
If you do not specify ConnCatalog=${catalog} in the JDBC connection URL, a default catalog is not set. Instead, you must include the catalog name in the query, as shown in the following example.select \* from catalog.schema.tableWhen you specify a catalog in the connection URL, you do not need to explicitly reference it when you query schema and data in the catalog, as shown in the following example.select \* from schema.table
Yes | Driver Name | String | The driver class name of your Databricks connection.
cdata.jdbc.databricks.DatabricksDriver
Yes | Port | Integer | The port number to establish a connection to the datasource.
The default port is 0
No | Limit Schemas | Option | Allows you to manage usage and restrict visibility to only the necessary schemas in the Explorer tree.
See Limiting schemas to learn how to limit schemas from the Connection Management page.
When you include a restricted schema in the query of a DQ Job, the query scope may be overwritten when the job runs. While only the schemas you selected when you set up the connection are shown in the Explorer menu, users are not restricted from running SQL queries on any schema from the data source.
No | Source Name | String | N/A |
| No | Target Agent | Option | The [Agent](/data-quality-self-hosted/installation/agent.md) that submits your Spark job for processing. |
| Yes | Auth Type | Option | The method to authenticate your connection.
The configuration requirements are different depending on the Auth Type you select. See Authentication for more details on available authentication types.
No | Properties | String | The configurable driver properties for your connection. Multiple properties must be semicolon-delimited, and each property=value pair, including the last one, must end with a semicolon (;). `abc=123;test=true;` |
| No | Variables | String | When you specify ${access\_token} in the Connection URL, set the following properties on the Variables tab.
Variable Name is set to access\_token.
Value is the password.
| | No | [Archive Break Records](/data-quality-self-hosted/core-concepts/findings/break-records-and-link-ids/archiving-break-records-from-pushdown-jobs.md) | Option | Allows you to write break records directly to a Databricks database or schema.
Ensure that you have the necessary privileges to write break records to Databricks.
Yes | Username | The username of your Databricks service account.
Set Username to token.
Yes | Password | The password of your Databricks service account.
Enter the token value that you entered in the Connection URL.
To successfully establish a Databricks connection, verify that your token is valid, because they generally expire in 90 days.
Yes | Username | The username of your Databricks service account.
Set Username to token.
Yes | Script | The file path containing the script file that the password manager uses to interact with and authenticate a user account.
:glasses-round: Example: /tmp/keytab/databricks\_pwd\_mgr.sh
No | Param $1 | Optional. An additional parameter to authenticate your Databricks connection. |
| No | Param $2 | Optional. An additional parameter to authenticate your Databricks connection. |
| No | Param $3 | Optional. An additional parameter to authenticate your Databricks connection. |
| {% endtab %} | | |
{% tab title="EntraID Service Principal" %}
| Required | Field | Description |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | -------------------------------------------- |
| Yes | Tenant ID | The tenant ID of your Microsoft account. |
| Yes | Client ID | The client ID of your Microsoft account. |
| Yes | Client Secret | The client secret of your Microsoft account. |
| {% endtab %} | | |
| {% endtabs %} | | |
## JDBC Driver Jar
If necessary, you can download the Databricks JDBC zip file from one of the following links.
* For the latest Databricks driver version, refer to the official [Databricks JDBC Driver](https://www.databricks.com/spark/jdbc-drivers-download) page.
* For archived Databricks driver versions, refer to the official [Databricks JDBC Driver archive](https://www.databricks.com/spark/jdbc-drivers-archive).
{% hint style="info" %}
Databricks JDBC driver version 3.4.2 is packaged as part of both standalone and Kubernetes download packages.
{% endhint %}
## Notebook (Supported)
* Pyspark SDK
* Scala SDK
* Example
Databricks no longer supports Runtime 6.5 or 10.3. Therefore, Collibra DQ Profile 2.45 is not runnable on Databricks.
[https://docs.databricks.com/release-notes/runtime/10.3ml.html](https://www.databricks.com/spark/jdbc-drivers-archive)
The following table shows the latest supported versions of Collibra DQ Profiles and their matching Databricks Runtimes.
## Spark Submit (Not Supported)
* Spark Master URL
* Databricks Jobs API
* Rest
* UI
* [DQ-Databricks Submit](/data-quality-self-hosted/apis/using-notebooks-with-data-quality-observability-classic/setting-up-collibra-dq-on-databricks/dq-databricks-submit.md)
{% hint style="info" %}
While these are not officially supported, there is a reference to architecture and implementation pattern for how to do a Databricks Job submission.
{% endhint %}
## Limitations
* When Archive Break Records is enabled for Azure Databricks Pushdown connections authenticated over EntraID, the data preview does not display column names correctly and shows 0 columns in the metadata bar. Therefore, Archive Break Records is not supported for Azure Databricks Pushdown connections that use EntraID authentication.
* UTF-8 character encoding for Databricks JDBC connections functions as expected in standalone deployments of Data Quality & Observability (self-hosted) versions older than 2024.06. As a workaround in versions older than 2024.06, follow the instructions in the [Collibra Support Portal](https://support.collibra.com/hc/en-us/articles/23026713519895-CDQ-findings-displays-certain-special-characters-as-question-mark-for-Databricks).
* Databricks connections that use Entra ID Service Principal authentication may fail with a duplicate-key error, such as "Multiple entries with same key: transportmode=http," after upgrading to Databricks driver version 3.4.1 or newer (introduced in 2026.06). This issue occurs if the connection URL includes the `transportMode` property with casing other than `transportMode`. Driver versions older than 3.x merge duplicate property keys with different casing, but driver 3.x and newer do not. To resolve this issue, update the connection URL to use the exact casing `transportMode`, then save the connection.