Google Cloud Enables Cross‑Engine Apache Iceberg Support in BigQuery

Why It Matters

The integration of Apache Iceberg with BigQuery removes a major barrier to adopting a unified lakehouse strategy. By enabling a single source of truth for both analytical and streaming workloads, organizations can cut storage redundancy, simplify data governance, and reduce the engineering overhead of maintaining parallel pipelines. This development also intensifies competition among the major cloud providers, each vying to become the default platform for open‑format data. For data engineers, the preview translates into a more flexible toolkit: they can choose the most appropriate compute engine for a given workload without worrying about data format conversion. The serverless catalog further abstracts infrastructure concerns, allowing teams to focus on business logic rather than catalog management. As more enterprises standardize on Iceberg, the ability to query the same tables from BigQuery and open‑source engines could drive broader adoption of Google Cloud’s analytics services.

Key Takeaways

• Google Cloud previewed a serverless Iceberg REST catalog for BigQuery.
• The catalog lets BigQuery, Spark, Flink and Trino query the same Iceberg tables.
• Eliminates the need for duplicate data copies across engines.
• Positions BigQuery against AWS and Azure lakehouse offerings.
• General availability slated for later 2026, pricing not yet disclosed.

Pulse Analysis

Google’s decision to embed Apache Iceberg directly into BigQuery reflects a strategic pivot toward open data formats that can bridge the gap between data warehouses and lakes. Historically, BigQuery has been a closed‑source warehouse, requiring data to be loaded into its proprietary storage before analysis. By embracing Iceberg, Google acknowledges that customers are increasingly building hybrid pipelines that blend batch, streaming and interactive workloads. The serverless catalog removes a traditional friction point—catalog provisioning—making it easier for enterprises to adopt a lakehouse without a steep operational learning curve.

From a competitive standpoint, the move narrows the differentiation between Google Cloud and its rivals. AWS introduced Iceberg support in Lake Formation earlier this year, and Azure Synapse has been expanding its open‑format capabilities. Google’s advantage lies in BigQuery’s reputation for low‑latency, high‑throughput SQL analytics; if performance parity can be demonstrated across external engines, the unified catalog could become a compelling reason for data teams to consolidate on Google Cloud. The real test will be how quickly the preview matures into a production‑ready service and whether pricing aligns with the cost expectations of large‑scale users.

Looking ahead, the broader industry trend points toward decoupling storage from compute while retaining a consistent metadata layer. As more organizations adopt Iceberg for its schema evolution and time‑travel features, the demand for cross‑engine query capabilities will rise. Google’s early entry positions it to capture a share of that demand, but success will depend on seamless integration, transparent pricing, and robust performance benchmarks that convince skeptical enterprises to shift critical workloads onto the platform.