AIToday
Large Language ModelsAI Business & IndustrySnowflake AI BlogPublished: Aug 5, 2026, 06:00 JST

Snowflake and Google Cloud pair Iceberg tables with AI governance

Snowflake and Google Cloud pair Iceberg tables with AI governance

3 Key Points

  1. What happened

    Snowflake and Google Cloud have aligned their data platforms around Apache Iceberg, an open table format that lets multiple engines (BigQuery, Apache Spark, Trino, Snowflake) read and write the same data without copying it. Snowflake's Horizon Catalog and Google Cloud's Lakehouse runtime catalog enable bidirectional federation—each platform's engines can access tables managed by the other through standardized REST API endpoints, with vended credentials controlling access.

  2. Why it matters

    Organizations no longer face a choice between flexibility (letting teams use different tools but risking data inconsistency) and consistency (forcing one engine but losing specialization). By anchoring both platforms to Iceberg and shared catalog governance, teams can pick the best tool for each job while central policies enforce security, access control and unified semantics. This matters especially for AI: Snowflake exposes model context protocol (MCP) servers so AI agents (Gemini Enterprise, code assistants) can query lakehouse data through the same governed channels humans use, while semantic models stored in the data layer (via Semantic View Autopilot and Semantic Studio) reduce AI hallucination by embedding verified business logic.

  3. What to watch

    Snowflake Horizon Context and Google Cloud's Knowledge Catalog embed business context (table descriptions, data quality signals, usage patterns) directly in the catalog so AI agents receive not just data but the surrounding knowledge needed to interpret it correctly—a distinction the body illustrates with the example of a grounded response ('Q4 revenue was $47.2M from the authoritative finance.revenue table') versus a generic one ('revenue might be...'). Semantic Studio's CoCo assistant is in private preview.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The article describes a convergence of two technical trends: interoperability and AI-readiness. For years, organizations faced a painful tradeoff—either let each team use its preferred engine (Apache Spark, BigQuery, Snowflake) and accept data fragmentation, or force everyone through a single system and lose specialization. Apache Iceberg, adopted across the industry, solved the first problem by establishing a shared physical layout so all engines can read and write the same tables without proprietary adapters. Snowflake and Google Cloud have now gone further by building managed catalogs (Horizon and Lakehouse runtime catalog) that federate across platform boundaries, using standardized REST APIs and short-lived, narrowly scoped storage tokens to enforce governance regardless of which engine accesses the data.

The second innovation addresses AI. Simply making data accessible is not enough; AI systems hallucinate when they lack semantic grounding—the business logic, definitions and context needed to interpret raw data correctly. Snowflake's Semantic View Autopilot and Semantic Studio (with a CoCo assistant in private preview) automatically discover and maintain semantic models from query patterns and user behavior, embedding business logic in the data layer rather than leaving it to AI prompts. Google Cloud's Knowledge Catalog provides similar contextual metadata through Gemini-powered insights. Both platforms expose these models and context to AI agents through model context protocol servers and REST APIs, ensuring agents inherit the same governance and semantic grounding as human analysts.

FAQ
What is Apache Iceberg and why do Snowflake and Google Cloud use it?
Apache Iceberg is an open table format developed by Netflix and donated to the Apache Software Foundation. It allows multiple engines—BigQuery, Apache Spark, Trino, Snowflake, Flink and others—to read and write directly to the same data in a customer's storage bucket without copying data between systems, solving the problem of data interoperability across multi-engine architectures.
Can Snowflake and Google Cloud access each other's data?
Yes. When Google Cloud manages the catalog via Lakehouse runtime catalog, Snowflake connects through a Catalog-Linked Database (CLD) that discovers and syncs tables from Google Cloud's REST API endpoints. Similarly, when Snowflake manages the catalog via Horizon, BigQuery and other Google Cloud engines connect to Horizon's REST endpoint and read/write Snowflake-managed Iceberg tables directly.
How do AI agents query lakehouse data?
Snowflake exposes model context protocol (MCP) servers that allow any MCP-compatible client—Gemini Enterprise, code assistants, custom agent frameworks—to discover and query lakehouse data through a universal interface. BigQuery also offers an MCP server. Both platforms also offer REST APIs for orchestration frameworks and embedded analytics.
Snowflake AI BlogRead Original Article

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleGitHub legal team built AI tools without coding