--- title: Lakehouse runtime catalog helps modernize Apache Hive description: Google Cloud describes its Lakehouse runtime catalog, a serverless metadata service built on the Apache Iceberg REST Catalog spec, positioned as a... canonical: https://daily.dev/posts/lakehouse-runtime-catalog-helps-modernize-apache-hive-hsxmm75px twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Lakehouse runtime catalog helps modernize Apache Hive | daily.dev og:description: Google Cloud describes its Lakehouse runtime catalog, a serverless metadata service built on the Apache Iceberg REST Catalog spec, positioned as a... og:url: https://daily.dev/posts/lakehouse-runtime-catalog-helps-modernize-apache-hive-hsxmm75px og:image: https://api.daily.dev/og/posts/HSxMM75PX.png og:image:alt: Lakehouse runtime catalog helps modernize Apache Hive og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Lakehouse runtime catalog helps modernize Apache Hive **[Google Cloud](https://daily.dev/sources/gcp)** · 5 min read · 0 upvotes · 0 comments ## Summary Google Cloud describes its Lakehouse runtime catalog, a serverless metadata service built on the Apache Iceberg REST Catalog spec, positioned as a zero-data-copy migration path off legacy Hive Metastore deployments. The post outlines pain points with standalone HMS (scaling bottlenecks, siloed security, operational overhead) and details how the new catalog enables multi-engine interoperability across Managed Spark, BigQuery, and Trino, plus integration with Knowledge Catalog and Cloud IAM for governance. It closes with a call to migrate Hive Metastore tables to Google Cloud. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How can I migrate my Apache Hive Metastore tables to Google Cloud without copying the underlying data? Google Cloud's Lakehouse runtime catalog supports a zero-data-copy migration: it connects directly to an existing self-managed Hive Metastore, extracts external table definitions and partition maps, and registers them into the serverless Lakehouse catalog. Table definitions point directly to existing data in Google Cloud Storage, so nothing is moved, rewritten, or duplicated, and tables become queryable via Managed Spark, BigQuery, and other Iceberg-compatible engines within minutes. _Teams weighing a Hive Metastore migration path can track lakehouse and Iceberg catalog developments on daily.dev._ ### What is the Google Cloud Lakehouse runtime catalog and how does it relate to Apache Iceberg? It is a fully serverless, highly available metadata registry that natively implements the Apache Iceberg REST Catalog specification while also supporting the Hive Catalog interface. It decouples metadata discovery from compute engines like Managed Spark, BigQuery, and Trino, letting multiple engines query the same underlying data without maintaining separate copies, and backs metadata storage with Google's Spanner infrastructure for scale. _Engineers comparing Iceberg catalog options can follow lakehouse architecture coverage on daily.dev._ ### Why do standalone Hive Metastore deployments become a bottleneck at large scale? Standalone HMS deployments rely on relational database backends like MySQL or PostgreSQL to track table schemas, partitions, and storage locations, and as data lakes grow to hundreds of thousands of partitioned tables, partition pruning and bulk listing operations create key performance bottlenecks. A complex Spark job requesting partition metadata can spike metastore CPU to 100%, causing cluster-wide query delays or out-of-memory failures. _Data platform teams debugging metastore scaling issues can find related architecture discussions on daily.dev._ ## Similar posts on daily.dev - [Lakehouse runtime catalog powered by Spanner](https://daily.dev/posts/lakehouse-runtime-catalog-powered-by-spanner-5i8ekjggr) · Google Cloud · 1 upvotes · 0 comments - [BigLake metastore now supports Iceberg REST Catalog](https://daily.dev/posts/biglake-metastore-now-supports-iceberg-rest-catalog-ne9xhokid) · Google Cloud · 0 upvotes · 0 comments - [ClickHouse integrates with Lakehouse Runtime Catalog](https://daily.dev/posts/clickhouse-integrates-with-lakehouse-runtime-catalog-jftljvyj2) · ClickHouse · 0 upvotes · 0 comments - [Couchbase Analytics \+ Apache Iceberg on Google Cloud: Query Your Lakehouse Without ETL](https://daily.dev/posts/couchbase-analytics-apache-iceberg-on-google-cloud-query-your-lakehouse-without-etl-l5aai8dvk) · Couchbase · 0 upvotes · 0 comments - [Unifying governance across engines and catalogs in the Open Lakehouse](https://daily.dev/posts/unifying-governance-across-engines-and-catalogs-in-the-open-lakehouse-qge5kcwda) · databricks · 0 upvotes · 0 comments --- Tags: [#gcp](https://daily.dev/tags/gcp), [#data-engineering](https://daily.dev/tags/data-engineering), [#apache-iceberg](https://daily.dev/tags/apache-iceberg) [View this post on daily.dev](https://daily.dev/posts/lakehouse-runtime-catalog-helps-modernize-apache-hive-hsxmm75px) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Lakehouse runtime catalog helps modernize Apache Hive","url":"https://daily.dev/posts/lakehouse-runtime-catalog-helps-modernize-apache-hive-hsxmm75px","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/lakehouse-runtime-catalog-helps-modernize-apache-hive-hsxmm75px"},"datePublished":"2026-08-19T16:08:51.747Z","dateModified":"2026-08-24T07:00:41.770Z","description":"Google Cloud describes its Lakehouse runtime catalog, a serverless metadata service built on the Apache Iceberg REST Catalog spec, positioned as a...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/9df795f90d3290a29c3b5ccad1c3e312?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/9df795f90d3290a29c3b5ccad1c3e312?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Google Cloud","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Google Cloud","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/gcp","url":"https://daily.dev/sources/gcp"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/lakehouse-runtime-catalog-helps-modernize-apache-hive-hsxmm75px","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"gcp,data-engineering,apache-iceberg","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Google Cloud","item":"https://daily.dev/sources/gcp"},{"@type":"ListItem","position":3,"name":"Lakehouse runtime catalog helps modernize Apache Hive"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/lakehouse-runtime-catalog-helps-modernize-apache-hive-hsxmm75px#faq","mainEntity":[{"@type":"Question","name":"How can I migrate my Apache Hive Metastore tables to Google Cloud without copying the underlying data?","acceptedAnswer":{"@type":"Answer","text":"Google Cloud's Lakehouse runtime catalog supports a zero-data-copy migration: it connects directly to an existing self-managed Hive Metastore, extracts external table definitions and partition maps, and registers them into the serverless Lakehouse catalog. Table definitions point directly to existing data in Google Cloud Storage, so nothing is moved, rewritten, or duplicated, and tables become queryable via Managed Spark, BigQuery, and other Iceberg-compatible engines within minutes. Teams weighing a Hive Metastore migration path can track lakehouse and Iceberg catalog developments on daily.dev."}},{"@type":"Question","name":"What is the Google Cloud Lakehouse runtime catalog and how does it relate to Apache Iceberg?","acceptedAnswer":{"@type":"Answer","text":"It is a fully serverless, highly available metadata registry that natively implements the Apache Iceberg REST Catalog specification while also supporting the Hive Catalog interface. It decouples metadata discovery from compute engines like Managed Spark, BigQuery, and Trino, letting multiple engines query the same underlying data without maintaining separate copies, and backs metadata storage with Google's Spanner infrastructure for scale. Engineers comparing Iceberg catalog options can follow lakehouse architecture coverage on daily.dev."}},{"@type":"Question","name":"Why do standalone Hive Metastore deployments become a bottleneck at large scale?","acceptedAnswer":{"@type":"Answer","text":"Standalone HMS deployments rely on relational database backends like MySQL or PostgreSQL to track table schemas, partitions, and storage locations, and as data lakes grow to hundreds of thousands of partitioned tables, partition pruning and bulk listing operations create key performance bottlenecks. A complex Spark job requesting partition metadata can spike metastore CPU to 100%, causing cluster-wide query delays or out-of-memory failures. Data platform teams debugging metastore scaling issues can find related architecture discussions on daily.dev."}}]} ```