Configure a catalog integration for files in object storage¶
Create a catalog integration for Apache Iceberg™ table files, Delta Lake table files, or Apache Parquet™ files in object storage.
After you create a catalog integration, you can create an Iceberg table.
Iceberg files¶
Create a catalog integration for Iceberg metadata that’s in an external cloud storage location
by setting OBJECT_STORE as the CATALOG_SOURCE value and ICEBERG as the TABLE_FORMAT.
Delta Lake table files¶
This integration is part of Delta Direct in Snowflake: you use it together with CREATE ICEBERG TABLE (Delta files in object storage) so that Snowflake can read Delta Lake tables in your bucket and optionally generate Iceberg metadata.
Create a catalog integration for Iceberg tables based on
Delta table files by setting OBJECT_STORE as the CATALOG_SOURCE value and DELTA as the TABLE_FORMAT.
CATALOG_SOURCE = OBJECT_STORETABLE_FORMAT = DELTA
Note
Snowflake doesn’t support creating Iceberg tables from Delta table definitions in other catalogs such as Databricks Unity Catalog or AWS Glue Data Catalog.
Parquet files¶
This integration is part of Parquet Direct in Snowflake: you use it together with CREATE ICEBERG TABLE (Parquet files in object storage) so that Snowflake can read Parquet files in your bucket in place, without a separate table format. For more information, see Parquet Direct.
Set OBJECT_STORE as the CATALOG_SOURCE value, and choose the TABLE_FORMAT that matches how your files are organized:
TABLE_FORMAT = HIVE: Your files use Hive-stylekey=valuedirectory partitioning (for example,year=2024/month=01/data.parquet). Snowflake infers partition columns from the paths.TABLE_FORMAT = NONE: Your files use any other layout. You can define partition columns explicitly by using expressions on theMETADATA$FILENAMEpseudocolumn.