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

FieldExampleNotes
Server URLhttps://trino.example.com:443Must include the scheme (https:// or http://) and the port
Usernamecredible
PasswordRequired with an https:// URL, unless you use a Peaka API key
CataloghiveOptional. The default catalog
SchemadefaultOptional. The default schema
Peaka API KeyOnly 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

ProblemCauseFix
The form will not save the server URLIt is missing the scheme or the portWrite it as https://host:port
Password not allowed for insecure authenticationA password was sent over http://Switch to the cluster's https:// URL
Access Denied: Cannot select from tableThe user lacks read access in Trino's access controlGrant access to the catalog, schema or table
Catalog '...' does not existThe Catalog value is wrong, or not visible to the userCheck the name with SHOW CATALOGS

Next Steps

On this page