LakeQL
Overview
  • Introduction
  • Datasource Contract
  • API Reference
Writing
  • Write Strategies
  • Load Strategies
  • Partitioning
Storage
  • Storage Operations
Trino
  • Connection
  • Write Config
  • Metadata
  • API Reference
Fabric
  • Connection
  • Metadata
  • API Reference
GitHub
LakeQL
  1. Data Sources
  2. Trino
  3. Metadata

Metadata

How the Trino adapter exposes catalogs, schemas, tables, and columns.

The Trino adapter inspects the cluster's metadata to discover what it can serve. The CLI introspection commands use this to list schemas, tables, views, and columns, and to generate typed endpoints with pull.

pnpm lakeql-cli list-schemas --source warehouse
pnpm lakeql-cli list-tables --source warehouse --schema sales
pnpm lakeql-cli list-columns --source warehouse --schema sales --table orders

Under the hood this maps to the same metadata operations the standalone trino-client exposes: schemas, tables, views, and columns. Complex column types are parsed into structured definitions that drive code generation. See Key Concepts for how introspected metadata becomes generated files.

Previous page

Write Config

Next page

API Reference