Trino

Trino is reached through the coordinator's HTTP protocol — the connection is provided by the trino-driver plugin (install it from the plugins page). Provide the coordinator host, a user name, and select a catalog (or catalog.schema) as the database.

Overview

TableR speaks the Trino client protocol over HTTP/HTTPS (default port 8080). Every request carries X-Trino-User, so a user name is always sent (default tabler); a password adds HTTP Basic auth for secured coordinators. The database field selects the session catalog — or catalog.schema to pin a schema too.

• Coordinator HTTP — connects to the coordinator on port 8080 (or 443/8443 over TLS).
• X-Trino-User — every request carries the user; it defaults to tabler when left empty.
• catalog[.schema] — the database field selects the session catalog and optional schema.
• Plugin-gated — the Trino card appears once the trino-driver plugin is installed.

Before you start

• The trino-driver plugin installed (Plugins → Trino → Install).
• The coordinator host and port (default 8080).
• A Trino user name (any string; defaults to tabler).
• Optional: a password when the coordinator enforces basic auth (usually over TLS).
• The catalog (or catalog.schema) to query, e.g. tpch.tiny.

Connection fields

These fields match TableR's Trino connection form. The password is stored in the operating system keyring, never in plain configuration files.

Connect with the form

1. 1
   Install the Trino plugin

   Open Plugins, find Trino, and install the trino-driver plugin.

2. 2
   Choose Trino

   Open the launcher and pick the Trino card.

3. 3
   Enter coordinator host and port

   Use your coordinator host and port (8080 for HTTP).

4. 4
   Set the user

   Any user name works — it is sent as X-Trino-User; defaults to tabler.

5. 5
   Pick a catalog

   Use the Database field for catalog or catalog.schema (e.g. tpch.tiny).

6. 6
   Enable SSL/TLS + password (optional)

   Turn on TLS and add a password when the coordinator enforces basic auth.

7. 7
   Save and connect

   Save the profile so it reappears in the launcher, then connect.

Verify the connection

Once connected, open a query tab and run SQL through the coordinator:

SELECT 1;
SHOW CATALOGS;

If both statements return, the coordinator, user, and credentials are all correct.

Troubleshooting

Next steps