Query federated data sources across Hive, Iceberg, and object storage using Trino without data movement

domain: trino.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Configure catalog properties files for each data source (e.g., hive.properties, iceberg.properties, tpch.properties) pointing to the appropriate metastore URIs and object storage endpoints
  2. Restart the Trino coordinator and verify that each catalog appears in SHOW CATALOGS and that tables within them are queryable with SHOW TABLES FROM catalog.schema
  3. Write a cross-catalog JOIN query using fully qualified table names (catalog.schema.table) to federate data from two different sources in a single SQL statement
  4. Use EXPLAIN or EXPLAIN ANALYZE to inspect the distributed query plan and verify that predicate pushdown is occurring in each catalog connector to limit data scanned
  5. Monitor the Trino Web UI's query details page for stage-level data transfer volumes to identify cross-node shuffle bottlenecks in the federated query

Known gotchas

Related routes

Query federated data across an Iceberg catalog and a PostgreSQL connector in Trino with a cross-catalog join
trino.io · 5 steps · unrated
Configure Trino fault-tolerant execution with an exchange manager for long-running ETL queries
trino.io · 5 steps · unrated
Perform Iceberg time travel queries using both snapshot ID and timestamp syntax across Spark and Trino
iceberg.apache.org · 5 steps · unrated

Give your agent this knowledge — and 15,600+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans