Trino Connections

Trino connections enable agents to run SQL against a Trino coordinator. Agents use the trino_query tool to execute reads across whichever catalogs the coordinator exposes (Hive, Iceberg, Postgres, MySQL, TPCH, etc.).

Recommended: Create and manage connections via the web UI at https://ui.cloud.firetiger.com/settings/connections

Network Configuration

Firetiger’s query servers must be able to reach your Trino coordinator. The same options as other database connections apply:

• Private network: Set up AWS PrivateLink, GCP Private Service Connect, or Azure Private Link (contact Firetiger support)
• Public coordinator with IP allowlist: Add Firetiger’s static IP addresses to your firewall (contact Firetiger support)
• Public coordinator with HTTPS: No additional networking needed

Connection Parameters

Required Parameters

Parameter	Type	Description
host	string	Trino coordinator host (e.g., trino.example.com)
port	int32	Trino coordinator port (443 for HTTPS, 8080 for HTTP)
catalog	string	Default catalog (e.g., hive, iceberg, tpch)
username	string	Username for authentication

Optional Parameters

Parameter	Type	Description	Default
schema	string	Default schema within the catalog	None
password	string	Password — Trino supports no-auth setups	None
secure	bool	Use HTTPS	true

Example Connection

{
  "display_name": "Analytics Warehouse",
  "description": "Trino coordinator over the analytics warehouse...",
  "connection_details": {
    "trino": {
      "host": "trino.example.com",
      "port": 443,
      "catalog": "iceberg",
      "schema": "warehouse",
      "username": "firetiger",
      "password": "<password>",
      "secure": true
    }
  }
}

Description Field

Document the catalogs, schemas, and key tables agents should know about. Trino’s federation means a single connection can span very different backends — listing them up front avoids agents calling SHOW CATALOGS and SHOW TABLES on every run.

Analytics Trino coordinator (Iceberg + Hive).

Catalogs:
- iceberg.warehouse: orders, customers, line_items (Iceberg, partition by event_date)
- hive.legacy: events_2023, events_2024 (Parquet, partition by dt)

Common patterns:
- Cross-catalog join: iceberg.warehouse.orders JOIN hive.legacy.events_2024
- Time bound: WHERE event_date >= DATE '2024-01-01'

Best Practices

• Use a dedicated read-only Trino user with SELECT privileges only
• Enable HTTPS (secure: true) for any non-local coordinator
• Document partition columns in the description so agents add the right WHERE predicates and avoid full-warehouse scans
• Prefer fully-qualified names (catalog.schema.table) in agent prompts to make queries portable across coordinators