Connecting to Trino

This section contains details for Trino connections.

General information

Field Description
Data source Trino
Supported versions 405.0
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

Minimum user permissions

In order to bring your Trino data into Collibra Data Quality & Observability, you need the following permissions.

  • Read access on your Trino database tables.
  • ROLE_ADMIN assigned to your user in Collibra DQ.

Recommended and required connection properties

Required Connection Property Type Value

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.

Example jdbc:trino://${host}:443/${catalogName}?SSL=true&source=jdbc:presto;ConnCatalog=${catalogName}

Important Your connection URL must contain the following substring: &source=jdbc:presto

Important 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

Source Name String N/A

No

Target Agent Option The Agent that submits your Spark job for processing.

Yes

Auth Type Option

The method to authenticate your connection.

Note 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 comma delimited. For example, 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.

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 Collibra Data Quality & Observability.

Steps

  1. Update the Connection URL to the following format: jdbc:trino://${host}:${port}/${catalog}?SSL=true&source=jdbc:presto&accessToken=${accessToken}
  2. Select Access Token Manager from the Authentication Type dropdown menu.
  3. Enter the User ID of the IdP account in the Username input field.
  4. Enter the file path containing the access token script file in the Script input field.
    For example, /opt/owl/config/get_trino.sh
  5. Click Submit.
Required Field Description

Yes

Username

The username of your Trino account.

The User ID of the IdP account.

Yes

Password The password of your Trino account.

Yes

Script

The file path containing the access token script file in the Script input field.

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.

Yes

Script

The file path containing the script file that the password manager uses to interact with and authenticate a user account.

Example /tmp/keytab/trino_pwd_mgr.sh

No

Param $1 Optional. An additional parameter to authenticate your Trino connection.

No

Param $2 Optional. An additional parameter to authenticate your Trino connection.

No

Param $3 Optional. An additional parameter to authenticate your Trino connection.

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 are not supported:
    • HYPERLOGLOG
    • P4HYPERLOGLOG
    • QDIGEST
    • SETDIGEST
    • TDIGEST