Trino
Trino / Starburst
Scan every catalog of a Trino or Starburst cluster — Iceberg, Delta Lake, Hudi, Hive and more.
- Category
- Warehouse & Lakehouse
- Source type
- TRINO
- Produces
- table
Trino is the query engine in front of many lakehouses, and one connection to it reaches every catalog it has configured. Starburst Galaxy and Starburst Enterprise connect the same way.
What you need to connect
Host and port of the coordinator, and a user. Sign in with a password, or with a JWT access token; leave both empty for a cluster with no authentication. Use HTTPS for anything outside a lab.
What Classifyre reads
Tables and views in every catalog and schema the user can see, or only the
catalogs and schemas you list. Trino’s own system catalog and
information_schema are skipped. Each table reports its format: iceberg,
delta, hudi, native for the engine’s own storage, or external.
Shared behaviour · SQL databases
One asset per table or view, never one per row. The asset carries the table's structure — database, schema, table name, object type, its columns and their types, and a row-count estimate — and its content is a sample of real rows, formatted so a detector reads actual values rather than a schema dump.
How many rows, and which ones, is entirely up to the sampling strategy. Large tables are paged through by key rather than by OFFSET, so a scan that stops halfway can resume from where it left off instead of re-reading from the top.
Read-only throughout. The connector issues catalog queries and bounded SELECTs. Nothing is written back, and a read-only account is the right account to give it.
Relationships come out of the engine's own catalog: a view and the tables it reads from are recorded as FLOW — real lineage, with column-level detail parsed out of the view's SQL where the SQL makes that possible. See Lineage.
Metadata on every asset
Asset kind · table
| Field | Type | Always present | What it is |
|---|---|---|---|
| database | string | Yes | Database or catalog name |
| table_name | string | Yes | Table name |
| table_type | string | Yes | Object type (TABLE/VIEW) |
| schema | string | No | Schema name |
| columns | object[] | No | Columns as {name, type} objects |
| row_count | integer | No | Estimated number of rows |
| table_format | string | No | Storage format of the table (iceberg, delta, hudi, paimon, lance, native, external, view) |
| object_type | string | No | Source object type |
| connector | string | No | Trino connector behind the catalog (iceberg, delta_lake, hive, ...) |
Lineage
Lineage
Views and the tables they read are recorded as lineage, parsed from the view SQL in Trino’s dialect. See Lineage & Relationships.
Worth knowing
- Each page of rows is one query. On a busy cluster, a smaller page size or a narrower scope keeps the scan light.
- The format comes from the catalog’s connector. A catalog that federates a
database, such as PostgreSQL, reports
native.
Configuration
Beyond the fields below, every source also has the settings shared by all of them: the sampling strategy, the augmentation notebook that enriches assets after extraction, the detectors to run, the scan schedule, and the compute limits for its scan jobs.
Required
Without these, the source will not save.
| Field | Type | Required | What it does | Default |
|---|---|---|---|---|
| required | object | Yes | —no extra properties | — |
| host | string | Yes | Coordinator host (Starburst Galaxy: <account>-<cluster>.trino.galaxy.starburst.io) | — |
| port | integer | Yes | Coordinator port (443 for Starburst Galaxy)min 1, max 65535 | 8080 |
Secrets
Stored encrypted and never shown again after you save them. See Configuration & Fields.
| Field | Type | Required | What it does | Default |
|---|---|---|---|---|
| masked | object | Yes | —no extra properties | — |
| access_token | string | No | JWT or OAuth access token, instead of a password | — |
| password | string | No | Password (basic authentication over HTTPS) | — |
| username | string | Yes | User to run queries as | — |
Optional
Everything you can tune. Sensible defaults apply when you leave them alone.
| Field | Type | Required | What it does | Default |
|---|---|---|---|---|
| optional | object | No | —no extra properties | — |
| connection | object | No | —no extra properties | — |
| connection.http_scheme | enum | No | http only for a local cluster without authentication Allowed: https, http | https |
| connection.request_timeout_seconds | number | No | Timeout for one querymin 1, max 3600 | 120 |
| connection.verify_ssl | boolean | No | Verify the coordinator's TLS certificate | true |
| extraction | object | No | —no extra properties | — |
| extraction.include_view_lineage | boolean | No | Read view definitions and record what each view selects from | true |
| scope | object | No | —no extra properties | — |
| scope.exclude_catalogs | array | No | Skip these catalogs (system is always skipped) | — |
| scope.exclude_catalogs[] | string | No | — | — |
| scope.exclude_schemas | array | No | Skip these schemas | — |
| scope.exclude_schemas[] | string | No | — | — |
| scope.include_catalogs | array | No | Only these catalogs | — |
| scope.include_catalogs[] | string | No | — | — |
| scope.include_objects | array | No | Only these objects (schema.table, or catalog.schema.table) | — |
| scope.include_objects[] | string | No | — | — |
| scope.include_schemas | array | No | Only these schemas | — |
| scope.include_schemas[] | string | No | — | — |
| scope.include_tables | boolean | No | Include tables | true |
| scope.include_views | boolean | No | Include views | true |
| scope.table_limit | integer | No | Maximum number of tables to scan per runmin 1 | — |