jdbc:trino://
Yes
No Yes Yes Yes Yes Yes Yes Yes Yes Yes| Field | Description |
|---|---|
| Data source | Trino |
| Supported versions | 1.0.50 |
| Connection string | jdbc:trino:// |
| Packaged? | Yes |
| Certified? | No |
| Supported features | |
| Estimate job | Yes |
| Analyze data | Yes |
| Schedule | Yes |
| 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 Trino connection.
When referring to the example below, replace the ${value} sections of the connection URL with your actual value.
jdbc:trino://${host}:443/${catalogName}?SSL=true\&source=jdbc:presto;ConnCatalog=${catalogName}
Your connection URL must contain the following substring: \&source=jdbc:presto
If your connection URL contains special characters and your Kubernetes deployment of Collibra DQ is a version before 2023.08, then you need to set the following Helm value to ensure you do not receive an invalid connection exception:--set 'global.web.security.xss.byPassUrls=/mirror/api,/v2/addconnection'
Yes | Driver Name | String | The driver class name of your Trino connection.
io.trino.jdbc.TrinoDriver
Yes | Port | Integer | The port number to establish a connection to the datasource.
The default port is 443
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.
Yes | Driver 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;` |
## Authentication
Select an authentication type from the dropdown menu. The options available in the dropdown menu are the currently supported authentication types for this data source.
{% tabs %}
{% tab title="Kerberos Password Manager" %}
| Required | Field | Description |
| ------------ | ----- | ----------- |
| {% endtab %} | | |
{% tab title="Kerberos Keytab" %}
| Required | Field | Description |
| ------------ | ----- | ----------- |
| {% endtab %} | | |
{% tab title="Kerberos Password" %}
| Required | Field | Description |
| ------------ | ----- | ----------- |
| {% endtab %} | | |
{% tab title="Password TGT Cache" %}
| Required | Field | Description |
| ------------ | ----- | ----------- |
| {% endtab %} | | |
{% tab title="Access Token Manager" %}
### Configuring Access Token Manager authentication
#### Prerequisites
You have added a script file that contains or can retrieve an access token to a folder accessible to Data Quality & Observability (self-hosted).
#### Steps
{% stepper %}
{% step %}
Update the Connection URL to the following format: `jdbc:trino://${host}:${port}/${catalog}?SSL=true&source=jdbc:presto&accessToken=${accessToken}`
{% endstep %}
{% step %}
Select **Access Token Manager** from the Authentication Type dropdown menu.
{% endstep %}
{% step %}
Enter the User ID of the IdP account in the Username input field.
{% endstep %}
{% step %}
Enter the file path containing the access token script file in the Script input field. For example, /opt/owl/config/get\_trino.sh
{% endstep %}
{% step %}
Click Submit.
{% endstep %}
{% endstepper %}
| Required | Field | Description |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Yes | Username | The User ID of the IdP account. |
| Yes | Script | The file path containing the access token script file in the Script input field.
:glasses-round: Example: /opt/owl/config/get\_trino.sh
No | Param $1 | Optional. Additional parameter. |
| No | Param $2 | Optional. Additional parameter. |
| No | Param $3 | Optional. Additional parameter. |
| {% endtab %} | | |
| {% endtabs %} | | |
## Limitations
* Trino connection URLs must contain the following substring: `&source=jdbc:presto`
* This requirement will be addressed in a future release.
* When using Pushdown for Trino, the following column [data types](/data-quality-self-hosted/connections/supported-connections/unsupported-data-types.md) are not supported:
* HYPERLOGLOG
* P4HYPERLOGLOG
* QDIGEST
* SETDIGEST
* TDIGEST