Trino
Connect a Trino cluster to Lakehousecat using a connection URI. Trino is a distributed SQL query engine that federates queries across multiple underlying data sources — including Hive, Iceberg, PostgreSQL, MySQL, and others — through a unified SQL interface.
Connection Fields
| Field | Required | Description |
|---|---|---|
| Connection URI | Yes | Full connection string including user, host, port, and catalog/schema. Example: trino://user@host:8080/catalog |
| Use SSH | No | Enable if the Trino coordinator is behind an SSH bastion host. When enabled, SSH settings fields appear: Host, Port, Username, Password, Private Key, and Private Key Passphrase. See SSH Tunneling. |
URI Format
trino://user@host:port/catalog
trino://user@host:port/catalog/schema
trino://user:password@host:port/catalog
Example (local development):
trino://admin@localhost:8080/memory
Prerequisites
- Admin or Builder role in Lakehousecat
- A Trino user with read access to the catalogs and schemas you want to expose
- Network connectivity from the Lakehousecat backend to the Trino coordinator (direct or via SSH)
Notes
- The catalog in the URI corresponds to a Trino connector (e.g.,
hive,iceberg,postgresql,memory). - Optionally append the schema to the URI to restrict the connection to a single schema.
- Use a read-only user or a user with restricted grants to follow the principle of least privilege.
- For large catalogs, configure schema and table filters in the Filters tab after creation to limit the scope of semantic extraction.
Next Steps
After creating the datasource, go to the Operations tab to trigger semantic extraction.