Trino
Connect a Trino cluster, or a Peaka-hosted one, to Credible
Credible connects to a Trino cluster over HTTP or HTTPS, with a username and password. For a cluster hosted by Peaka, it signs in with a Peaka API key instead.
Connection Fields
| Field | Example | Notes |
|---|---|---|
| Server URL | https://trino.example.com:443 | Must include the scheme (https:// or http://) and the port |
| Username | credible | |
| Password | Required with an https:// URL, unless you use a Peaka API key | |
| Catalog | hive | Optional. The default catalog |
| Schema | default | Optional. The default schema |
| Peaka API Key | Only for Peaka-hosted Trino. Use it instead of a password, catalog and schema |
Use an https:// URL. With http:// the connection, password included, is not encrypted, so Trino accepts no password over it: http:// suits only a cluster without authentication on a private network.
Permissions
The user needs read access to the catalogs and schemas you plan to model, under whatever access control your cluster uses (file-based rules, Ranger or similar).
From the CLI
To add the connection with cred add connection, put an entry like this in the JSON file:
[
{
"name": "warehouse",
"type": "trino",
"trinoConnection": {
"server": "https://trino.example.com:443",
"user": "credible",
"password": "...",
"catalog": "hive",
"schema": "default"
}
}
]server is the full server URL, scheme and port included. For Peaka, use peakaKey instead of password, catalog and schema.
Troubleshooting
| Problem | Cause | Fix |
|---|---|---|
| The form will not save the server URL | It is missing the scheme or the port | Write it as https://host:port |
Password not allowed for insecure authentication | A password was sent over http:// | Switch to the cluster's https:// URL |
Access Denied: Cannot select from table | The user lacks read access in Trino's access control | Grant access to the catalog, schema or table |
Catalog '...' does not exist | The Catalog value is wrong, or not visible to the user | Check the name with SHOW CATALOGS |