Data catalogs

Query Iceberg tables in AWS Glue, BigLake, OneLake, Polaris, Unity Catalog or any Iceberg REST catalog in place, without copying them.

Connect a catalog and Contrast mounts it as a read-only database. Its namespaces are the database's schemas, so SELECT * FROM lake.sales.orders reads sales.orders in the catalog as it is when the query runs. Lakeserve reads the table's files from your storage; nothing is copied into Contrast, and Contrast never writes to your catalog or storage.

Connect a catalog

Workspace owners and admins open Sources → Direct → Data catalogs → Add a catalog, choose the catalog, fill in its connection parameters and name the database. Contrast checks the connection the way queries will use it before saving anything: it signs in, lists namespaces and tables, loads a table and reads its metadata file with the storage credentials a query would get. A failed check saves nothing and says what to fix.

CatalogParametersHow table files are read
AWS GlueRegion; an access key, or an IAM roleThe same AWS identity
BigLake MetastoreGoogle ADC client ID, client secret and refresh token, quota project, Cloud Storage bucketCredentials BigLake vends, else the same Google identity
Microsoft OneLakeFabric workspace ID, lakehouse (data item) ID, Entra tenant ID, application ID and secretThe same Entra application
Polaris (Snowflake Open Catalog)Account host, catalog name, principal client ID and secret, optional storage endpointCredentials the catalog vends
REST CatalogCatalog URL, warehouse, optional storage endpoint; OAuth client credentials or a bearer tokenCredentials the catalog vends
Unity CatalogWorkspace URL, catalog name, service principal client ID and OAuth secretCredentials Unity Catalog vends

AWS Glue with an IAM role

Choose AWS IAM role and add the principal and external ID the form shows to your role's trust policy. The external ID is unique to your workspace. The role needs glue:GetCatalog, glue:GetDatabase(s) and glue:GetTable(s) on the databases and tables to expose, and s3:GetObject and s3:ListBucket on their storage.

Unity Catalog

Create a service principal and an OAuth secret for it (a secret scoped to unity-catalog read access is enough). Grant it USE CATALOG on the catalog and USE SCHEMA, SELECT and EXTERNAL USE SCHEMA on each schema, and turn on External data access for the metastore. Tables in Databricks default storage (serverless workspaces) cannot be read by any external engine; keep the catalog's managed location on your own cloud storage. Contrast reads the catalog's Iceberg tables.

Polaris and other REST catalogs

The principal's role needs read privileges on the catalog, and the catalog must vend storage credentials (X-Iceberg-Access-Delegation: vended-credentials). A storage endpoint, when given, limits reads to tables under it.

Query

SHOW SCHEMAS IN lake;
SHOW TABLES IN lake.sales;
SELECT customer, sum(amount) FROM lake.sales.orders GROUP BY customer;

Names are case-insensitive and are matched to the catalog's spelling. Quote names with other characters, such as lake.`sales-eu`.orders, and a nested namespace as one name, lake.`sales.eu`.orders. Each query reads every table's current snapshot, so new commits are visible immediately. Connected catalogs are read-only: writes, ingestion into them and table maintenance stay with the catalog's owner.

Disconnect

Disconnect removes the database and its stored credentials. Your catalog and data are untouched.