Connect to Trino
Connect to a Trino or Presto coordinator over HTTP(S) with a password, JWT, browser OAuth2 or Kerberos, optionally through SSH.
A Trino connection is the URL of the coordinator, an HTTP or HTTPS address with no user, password or query string in it. Tablyne talks to the coordinator over its REST protocol, so there is no driver to install.
Trino or Presto
Tablyne reads the server version to tell Trino from Presto. If a proxy hides the version, you can set the flavor in the form.
Authentication
- No authentication, over plain HTTP, only if you choose it. A production connection refuses HTTP.
- User and password, over HTTPS only.
- A JWT token, stored in the system keychain and sent over HTTPS.
- OAuth2 in the browser. Tablyne opens the sign-in page, waits up to five minutes and keeps the token in memory only. The sign-in addresses must be on the same host as the connection, or Tablyne refuses them.
- Kerberos, using the ticket from
kinit, over verified HTTPS. It is available on macOS and Linux, not on Windows. You can set the service name; the default istrino.
Other settings
You can set a default catalog and schema, a session time zone, a connection timeout and a session user, which runs queries as another user you are allowed to act as. You can add a CA certificate in PEM format; the server certificate is always verified. An SSH tunnel is available when the coordinator is not reachable directly.
Limits per run
The form also holds the per-run limits and the choice of when to estimate a read. Those are described under safe mode.
Testing
The test connects to the coordinator and shows the server version, the host and the round-trip time. Tablyne does not keep a session on the server: each tab sends its own catalog and schema with every request.