BigData / Apache Iceberg Interview questions
What is an Iceberg catalog?
A catalog is the component that maps a table name to the location of its current metadata file, serving as the single source of truth for "what is the current state of this table" that every reader and writer consults before doing anything else.
| Catalog Type | Notes |
| Hive Metastore | Uses the existing Hive Metastore service to track table pointers |
| AWS Glue | Uses AWS Glue Data Catalog as the pointer-tracking service |
| REST Catalog | A standardized HTTP API for catalog operations, engine-agnostic |
| JDBC / Nessie | A relational database, or Nessie's Git-like versioned catalog, as the backing store |
Whichever catalog implementation is used, its core job is the same: atomically updating the pointer from an old metadata file to a new one when a commit happens, ensuring that concurrent readers always see either the fully-old or fully-new table state, never a partially-applied, inconsistent one.
Because the catalog is decoupled from the actual data storage, different catalog implementations can be swapped without touching the underlying data files themselves, which is part of what makes Iceberg's multi-engine, multi-tool interoperability practical — different tools just need to agree on which catalog to consult.
More Related questions...