# Databricks, Google stop copying lakehouse data _Databricks and Google now let BigQuery and Unity Catalog read one copy, and push Iceberg labels to carry governance._ **Published:** 2026-11-17 **Source:** https://www.startuphub.ai/ai-news/technology/2026/databricks-google-stop-copying-lakehouse-data --- Parth Desai, Alex Jiang and John Spencer, writing for [Databricks](https://www.databricks.com/blog/advancing-catalog-interoperability-unity-catalog-and-google-clouds-borderless-lakehouse), announced bidirectional access between Unity Catalog and Google's lakehouse. The company said customers can query the same copy from either BigQuery or Databricks without duplication. No copies move. In one direction, [Databricks](https://www.startuphub.ai/startups/databricks) mounts Iceberg tables from Google's Lakehouse runtime catalog for use in its warehouse or Genie. The company said those tables can run in its serverless warehouse or Genie. Genie is its natural-language tool that [recently learned to package team habits as skills](/ai-news/artificial-intelligence/2026/databricks-turns-team-habits-into-genie-skills). In the other direction, BigQuery can read Unity Catalog managed tables without a copy, the authors said. The next push is metadata, not storage. The authors said they helped land catalog labels in Iceberg, key-value pairs that travel with the table. A table tagged domain=finance and status=certified keeps those tags when federated, as does a column tagged pii=ssn. That persistence matters for masking and for agents hunting context, they said. That framing is narrower than federation already in the docs. Per [Databricks docs](https://docs.databricks.com/aws/en/query-federation/), Lakehouse Federation splits into query federation and catalog federation, with query federation covering MySQL, PostgreSQL, Teradata and Oracle. Per [Google's lakehouse docs](https://docs.cloud.google.com/lakehouse/docs/key-concepts), another path syncs SAP BDC shares via Delta Sharing for BigQuery queries. This deal extends the catalog side, not the query side. The authors did not say who enforces a label when two catalogs disagree, or what writes, latency and cost look like across the boundary. They pitched shared governance that travels with data and does not need redefinition in each system. Who wins when the same column is certified in one catalog and restricted in the other? --- Original analysis from [startuphub.ai](https://www.startuphub.ai), the #1 AI startup directory. © StartupHub.ai. All rights reserved. You may not republish this article in full without a license. Search engines and AI research tools may crawl and summarize for reference. Bulk reproduction or model training on this content requires a license. See https://www.startuphub.ai/terms.