BigLake Metastore Lakehouse runtime catalog
Legacy names BigLake Metastore, BigQuery metastore
Managed Apache Iceberg REST catalog and Hive metastore component of Google Cloud Lakehouse.
Naming timeline
- BigLake Metastore
Serverless metastore for open-format tables on BigLake (later designated BigLake metastore (classic) when BigQuery metastore was renamed BigLake metastore at GA on June 3, 2025).
- Lakehouse runtime catalogCurrent name
Rebranded from BigLake metastore to Lakehouse runtime catalog on April 20, 2026.
What is BigLake Metastore called now?
BigLake Metastore is now called Lakehouse runtime catalog, with the latest change on 20 April 2026 (Google Cloud Next '26). Earlier names covered by this entry also include BigQuery metastore. Managed Apache Iceberg REST catalog and Hive metastore component of Google Cloud Lakehouse. Only the customer-facing name changed; the underlying technical identifiers remain backward compatible.
Also known as
- Lakehouse Iceberg REST catalog
- BigLake metastore (classic)
Technical identifiers
Technical identifiers unchanged. Only the customer-facing product name changed; the APIs, CLI commands, IAM roles and Terraform resources below keep their legacy identifiers for backward compatibility.
| REST / gRPC APIs | biglake.googleapis.com |
|---|---|
| gcloud / CLI Commands | gcloud biglake |
| IAM Predefined Roles | roles/biglake.* |
| Terraform Resources | google_biglake_* |
Managed via biglake.googleapis.com and gcloud biglake commands.
Notes & disambiguation
- As of April 20, 2026, BigLake metastore is officially called the Lakehouse runtime catalog.
- Previously, the next-generation serverless metastore launched in Preview as BigQuery metastore (January 21, 2025) before being renamed BigLake metastore at GA on June 3, 2025 (when the older metastore became 'BigLake metastore (classic)').
- Distinct from Dataproc Metastore (which retains its legacy name) and Knowledge Catalog.
Sources & official documentation
Catalog last updated . Spotted an error? Suggest an edit