Snowflake-Labs/state-of-iceberg

Snowflake-Labs/state-of-iceberg

Description: An interactive visualization of Iceberg engine, catalog, and platform compatibility

Language: TypeScript

License: Apache-2.0

Stars: 1

Forks: 0

Open issues: 0

Created: 2026-04-02T16:26:56Z

Pushed: 2026-05-19T21:31:03Z

Default branch: main

Fork: no

Archived: no

README:

The State of Iceberg

https://stateoficeberg.org/

An interactive explorer of Apache Iceberg interoperability across the modern data ecosystem. Discover which platforms, engines, and catalogs can connect, and how.

The Iceberg ecosystem spans dozens of platforms, catalogs, and engines — each with different levels of support. This tool exists to make Iceberg interoperability understandable. Contributions and corrections are welcome. The accuracy of this project will improve when the community participates.

Run Locally

npm install
npm run dev

Open http://localhost:3000.

Project Structure

├── app/ # Next.js App Router pages
├── components/graph/ # Sigma.js graph, drawer, legend
├── data/
│ ├── catalogs/ # One YAML file per catalog (10)
│ ├── engines/ # One YAML file per engine (12)
│ └── platforms/ # One YAML file per platform (9)
├── lib/
│ ├── types.ts # TypeScript type definitions
│ ├── data.ts # YAML data loader
│ └── graph-data.ts # Graph serialization helpers
└── .gitignore

How the Data Works

All platform, engine, and catalog data lives in YAML files under data/. Each file follows a structured schema defining:

• Identity: name, type (catalog / engine / platform), vendor, open source status
• Spec support: which Iceberg spec versions (v1, v2, v3) are supported
• DML: which SQL operations are supported (INSERT, UPDATE, DELETE, MERGE)
• Capabilities: schema evolution, partition evolution, time travel, row-level deletes, branching/tagging, views, streaming
• Maintenance: compaction, snapshot expiry, orphan cleanup
• Catalog integrations: which catalogs this platform/engine connects to, and in what mode (read, write, read_write)

The YAML files are read at build time and used to generate the interactive graph and all detail views.

Nodes

Catalogs (11): Polaris, Nessie, AWS Glue, HMS, Unity Catalog, S3 Tables, Lakekeeper, Gravitino, BigLake Metastore, OneLake, Horizon

Engines (12): Spark, Trino, Presto, Flink, Hive, Impala, DuckDB, StarRocks, ClickHouse, Doris, Kafka Connect, RisingWave

Platforms (9): Snowflake, Databricks, BigQuery, Athena, Redshift, Fabric, Dremio, Cloudera CDP, Oracle

Contributing

To update a platform's capabilities:

1. Edit the relevant YAML file in data/ 2. Update the last_verified date 3. Submit a pull request

Tech Stack

• Next.js (App Router, TypeScript)
• Sigma.js + Graphology (graph visualization)

License

Apache 2.0 — see [LICENSE](LICENSE) for details.