Trino
Catalog every catalog mounted on a Trino cluster (Hive, Iceberg, Delta Lake, relational connectors) from information_schema.
Capabilities
| Capability | Support | Notes |
|---|---|---|
| Tables, views & columns | Supported | Each Trino catalog exposes its own information_schema: one extraction query per catalog or a UNION across catalogs. |
| Keys, constraints & indexes | Not available | |
| Procedures & functions | Not available | |
| Data lineage | Partial | |
| Lineage from query history | Not available | |
| Business glossary links | Supported | |
| Data quality probes | Supported | |
| Data profiling | Supported | |
| Data classification | Supported | |
| Chat with your data | Supported |
Connection settings
Create the connection on the Blindata Agent from Settings > Agents > Connections with the connection wizard, choosing Trino in the technology step.
| Driver class | io.trino.jdbc.TrinoDriver |
|---|---|
| JDBC URL | jdbc:trino://localhost:8080/<catalog> |
| Authentication |
Service principal (shared technical user) User principal (personal credentials, BYOC) Ephemeral credentials (asked at each run)
|
| Crawling strategy | SQL |
The Blindata Agent does not include this driver: download the vendor JDBC driver and copy the .jar into the agent drivers folder, as described in
Add JDBC drivers.
Driver properties can be added under Advanced settings in the connection wizard.
Prerequisites & permissions
- A Blindata Agent installed with network access to Trino.
- The vendor JDBC driver installed on the agent (see Add JDBC drivers).
- A user allowed by the Trino access control to list schemas and tables of the catalogs to document.
Set up metadata crawling
- Create the connection to Trino on the agent (see Connection settings) and use Test to verify it.
- Create or open the system that represents Trino in the catalog and link it to the connection.
- In the CRAWLING tab add a crawling job with strategy SQL and, if needed, replace the default queries with the ones suggested below.
- Run a TEST to check the number of extracted objects, then RUN or schedule the job.
The job options and the column aliases of every extraction query are described in the Generic JDBC reference.
Lineage through OpenLineage
Trino has an OpenLineage event listener. Configured with the address of the Blindata Agent, it sends the lineage of queries to the OpenLineage connector , which publishes it on the tables you crawl from the Trino catalogs.
What the listener emits and Blindata uses:
- Inputs and outputs of the queries it reports give table lineage. By default the listener reports
DELETE,INSERT,MERGE,UPDATEandALTER_TABLE_EXECUTEqueries. trino_metadata,trino_query_context,trino_query_statistics: the query id is stored as a property of the job, the rest is ignored.
Each query is a job, named by its query id unless you change the listener’s job name format. Configuration: Configure your producers . Facet by facet: Facet support reference .