BigQuery, Spark, and Trino Can Now Query the Same Iceberg Table on GCP

A technical demonstration on Google Cloud Platform shows how BigQuery, Apache Spark, and Trino can simultaneously read and write a single Apache Iceberg table without duplicating data. The setup uses Google Cloud's Lakehouse for Apache Iceberg service — formerly known as BigLake — which provides a native REST Catalog to coordinate table versions across query engines. Apache Iceberg acts as an open metadata layer over Parquet files stored in Google Cloud Storage, enabling ACID transactions, time travel, and schema evolution. The approach directly addresses a common enterprise problem where separate teams store redundant copies of the same data in different tools, leading to higher storage costs, inconsistent records, and fragmented access controls. The experiment was validated on real GCP infrastructure, including a captured HTTP 409 conflict error demonstrating Iceberg's optimistic concurrency control in action.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in