Trino

Connect & Ingest data from / to a Trino database

Setup

The following credentials keys are accepted:

  • http_url (required) -> The url to use to connect (examples: http://user:password@localhost:8080?catalog=memory&schema=test)

  • catalog (required) -> The database / catalog name of the instance

  • schema (optional) -> The default schema to use

  • source (optional) -> Source of the connection

  • session_properties (optional) -> Session properties, as a map[string]string

  • extra_credentials (optional) -> Extra credentials, as a map[string]string

  • custom_client_name (optional) -> Custom client name

  • kerberos_enabled (optional) -> KerberosEnabled (default is false)

  • kerberos_keytab_path (optional) -> Kerberos Keytab Path

  • kerberos_principal (optional) -> Kerberos Principal used to authenticate to KDC

  • kerberos_realm (optional) -> The Kerberos Realm

  • kerberos_config_path (optional) -> The krb5 config path

  • ssl_cert_path (optional) -> The SSL cert path on local disk for TLS verification

  • ssl_cert (optional) -> The SSL cert string value for TLS verification

  • skip_tls (optional) -> Whether to skip TLS verification (specify true).

  • query_timeout (optional since 1.2.21) -> The number of minutes to timeout a query (default is 360).

  • use_adbc (optional) -> Enable Arrow Database Connectivity (ADBC) driver for high-performance data transfer. See ADBC for setup and details. (v1.5.2+)

  • adbc_uri (optional) -> Override the automatically constructed ADBC connection URI when using use_adbc=true.

Using sling conns

Here are examples of setting a connection named TRINO. We must provide the type=trino property:

Environment Variable

See here to learn more about the .env.sling file.

Sling Env File YAML

See here to learn more about the sling env.yaml file.

If you are facing issues connecting, please reach out to us at [email protected]envelope, on discordarrow-up-right or open a Github Issue herearrow-up-right.

Last updated

Was this helpful?