Trino

Access configuration details to connect Soda to a Trino data source.

Soda uses the official Trino Python client internally to establish connections and execute queries.

Connection configuration reference

Install the following package:

pip install soda-trino

Data source YAML

Core connection

Create the config file:

soda data-source create -f ds_config.yml

Configure connection

To connect to Trino, add a data_source block to your ds_config.yml file.

Authentication method	Soda Cloud support	Soda Core support
Username/password	✅	✅
JWT (existing token)		✅
JWT (OAuth – client credentials flow)	✅	✅
No authentication		✅

Core connection parameters

Parameter	Required	Default	Description
type	Yes	—	Must be trino.
host	Yes	—	Hostname or IP address of the Trino coordinator.
catalog	Yes	—	Trino catalog name.
verify	No	True	SSL verification. Supported in Soda Core only.

1. Username/password

Supported in Soda Cloud and Soda Core.

ds_config.yml

type: trino
name: my_trino
connection:
  host: trino.example.com
  catalog: hive

  # Optional connection settings
  port: 443
  http_scheme: https
  source: soda-core
  client_tags: ["dq", "prod"]

  # Authentication
  # auth_type: BasicAuthentication  # Optional
  user: ${TRINO_USER}
  password: ${TRINO_PASSWORD}

Parameter	Required	Default	Description
port	No	443	Trino port.
http_scheme	No	https	One of http, https.
source	No	soda-core	Trino-internal label for the connection.
client_tags	No	—	Trino-internal tags for this connection.
auth_type	Depends	—	Authentication type. See modes above.
user	Username/password	—	Trino username.
password	Username/password	—	Trino password.

---

2. JWT (existing token)

Supported in Soda Core only.

ds_config.yml

type: trino
name: my_trino
connection:
  host: trino.example.com
  catalog: hive

  auth_type: JWTAuthentication
  access_token: ${TRINO_JWT_ACCESS_TOKEN}

Parameter	Required	Default	Description
auth_type	Depends	—	Authentication type. See modes above.
access_token	JWT (existing token)	—	JWT access token.

---

3. JWT (OAuth – client credentials)

Supported in Soda Cloud and Soda Core.

type: trino
name: my_trino
connection:
  host: trino.example.com
  catalog: hive

  auth_type: OAuth2ClientCredentialsAuthentication
  oauth:
    token_url: https://auth.example.com/oauth2/token
    client_id: ${TRINO_OAUTH_CLIENT_ID}
    client_secret: ${TRINO_OAUTH_CLIENT_SECRET}
    scope: "scope1 scope2"         # Optional
    grant_type: client_credentials

Parameter	Required	Default	Description
auth_type	Depends	—	Authentication type. See modes above.
oauth	JWT (OAuth)	—	OAuth configuration block.
oauth.token_url	JWT (OAuth)	—	OAuth token endpoint.
oauth.client_id	JWT (OAuth)	—	OAuth client ID.
oauth.client_secret	JWT (OAuth)	—	OAuth client secret.
oauth.scope	No	null	Space-separated scopes.
oauth.grant_type	No	client_credentials	OAuth grant type.

---

4. No authentication

Supported in Soda Core only.

type: trino
name: my_trino
connection:
  host: trino.example.com
  catalog: hive
  port: 8080
  http_scheme: http

  auth_type: NoAuthentication

---

Test the connection

To test your connection configuration:

soda data-source test -ds ds_config.yml

---

Limitations & edge cases

Using Trino as a Diagnostics Warehouse destination through between-source copying is available but not fully supported.

There is a known issue when the Trino catalog is Iceberg-based. You are advised to:

• Use within-source copying, or
• Configure Soda to connect directly to the destination data source instead of routing through the Trino catalog connection.

---

You are not logged in to Soda and are viewing the default public documentation. Learn more about Licensing & documentation access.

If you do have a Soda license, make sure to log in to Soda Cloud in this same browser.