Iceberg Tables

NOTE: This feature requires Quilt Platform version 1.70.0 or higher.

Quilt automatically maintains Apache Iceberg tables that provide high-efficiency, externally queryable access to package information. This is particularly useful for buckets that contain thousands of packages or for queries that span multiple buckets.

You can query package revisions, tags, file entries, and metadata using Amazon Athena or external data warehouses that support Iceberg (e.g., Databricks, Snowflake).

Tables

For each bucket registered with Quilt, four per-bucket tables are maintained in the Iceberg Glue database, whose name is exposed as the IcebergDatabaseName output in your CloudFormation stack:

• {bucket}_package_revision — package revisions with timestamps

• {bucket}_package_tag — named package tags (currently only latest)

• {bucket}_package_manifest — package-level metadata and commit messages

• {bucket}_package_entry — individual file entries within packages

The bucket is encoded in the table name, so the tables do not carry a bucket column. Because S3 bucket names can contain hyphens, the resulting Glue table names (e.g. my-bucket_package_tag) must be double-quoted in Athena SQL, as shown in the examples below.

Every Quilt role automatically receives Athena read access to the per-bucket tables for the buckets it can read — managed users are scoped to their readable buckets via the registry-applied session policy; non-managed roles have stack-wide access by design.

Admin note — Lake Formation. If AWS Lake Formation enforcement is enabled on your account (data lake), you must set the EnableLakeFormationGrants CloudFormation parameter to true so the stack emits the PrincipalPermissions (Lake Formation) grants its service roles need to reach the data lake. This is opt-in and off by default: if your account enforces Lake Formation but the stack has not enabled these grants, Lake Formation denies the stack and per-bucket Iceberg access (among other things) breaks. Leave the parameter off only on accounts that do not enforce Lake Formation.

Finding the tables in the Queries tab

As of Quilt Platform 1.71.0, managed users can select the Iceberg package-index database directly from the Database dropdown in the catalog's Queries tab, instead of typing its fully-qualified name.

Example: Get entries and metadata for the latest version of a package

SELECT
  e.logical_key,
  e.physical_key,
  e.size,
  e.metadata
FROM "my-bucket_package_tag" t
JOIN "my-bucket_package_entry" e
  ON t.top_hash = e.top_hash
WHERE t.pkg_name = 'analytics/results'
  AND t.tag_name = 'latest'

Example: Find latest packages matching specific metadata

SELECT
  t.pkg_name,
  t.tag_name,
  m.metadata
FROM "my-bucket_package_tag" t
JOIN "my-bucket_package_manifest" m
  ON t.top_hash = m.top_hash
WHERE t.tag_name = 'latest'
  AND json_extract_scalar(m.metadata, '$.experiment_id') = 'EXP-123'
  AND json_extract_scalar(m.metadata, '$.status') = 'complete'

Cross-bucket queries

To search across multiple buckets, UNION ALL the per-bucket tables explicitly:

SELECT 'bucket-a' AS bucket, pkg_name, tag_name, top_hash
FROM "bucket-a_package_tag"
WHERE tag_name = 'latest'
UNION ALL
SELECT 'bucket-b' AS bucket, pkg_name, tag_name, top_hash
FROM "bucket-b_package_tag"
WHERE tag_name = 'latest'

See also

• Query: Use the Catalog's Queries tab

• Athena: Query package manifests using AWS Athena

• Tabulator: Query tabular data within packages