The Fabric adapter inspects the warehouse's metadata to discover what it can serve. The CLI introspection commands work the same way against a Fabric data source as they do against Trino. Pass the configured source name:
pnpm lakeql-cli list-schemas --source reportingpnpm lakeql-cli list-tables --source reporting --schema salespnpm lakeql-cli list-columns --source reporting --schema sales --table ordersLike the Trino adapter, the Fabric adapter builds its own SQL for metadata rather than calling a client convenience method: sys.databases for catalogs, and INFORMATION_SCHEMA.SCHEMATA / TABLES / COLUMNS for schemas, tables, views, and columns. The difference is one level down. The standalone trino-client package additionally exposes its own schemas()/tables()/views()/columns() convenience methods for callers using it directly outside the adapter. fabric-client has no equivalent.
Catalog listing filters out the fixed SQL Server system databases (
master,
tempdb, model, msdb). Schema listing filters out sys,
INFORMATION_SCHEMA, guest, queryinsights, and _rsc, plus any schema
matching the db_* role-schema pattern (for example, db_owner), so only
user-facing schemas are returned. Column discovery reports name and type, but
the adapter always returns description: undefined. Trino maps a comment
column; Fabric's column query has no equivalent mapped in.