Open lakehouse governance: what bi-directional metadata sync changes

TL;DR: Business context, lineage, ownership and compliance can stay aligned across an open lakehouse through bi-directional metadata synchronization between Collibra and Google Cloud Knowledge Catalog, so data teams can trust what they are using for AI and operational decisions, according to Collibra. The practical issue is not catalog coverage alone, but whether governance and technical reality stay synchronized as data estates change.

NHIMG editorial — what this means for NHI practitioners

Questions worth separating out

Q: How should organisations govern data for AI when business context lives in one system and technical metadata lives in another?

A: They should treat synchronization between governance and platform metadata as a control requirement.

Q: Why does bi-directional metadata sync matter in open lakehouse environments?

A: Open lakehouses move quickly across distributed storage and analytics layers, so one-way governance leaves stale records behind.

Q: What breaks when data governance lacks business context?

A: Teams lose the ability to judge whether data is authoritative, who is accountable for it and what level of trust is justified.

Practitioner guidance

• Map metadata ownership to governance responsibilities Document which team owns lineage, definitions, quality and policy for each high-value dataset, then verify that those attributes are present in both the governance layer and the cloud catalog.
• Validate bidirectional sync before expanding AI use Test that changes in the governance system appear in the cloud fabric and that technical discovery changes return to the system of record.
• Tie access decisions to business context Require lineage, quality and ownership signals before approving sensitive analytics access or downstream AI consumption.

What's in the full announcement

Collibra's full article covers the operational detail this post intentionally leaves for the source:

• The exact bi-directional integration flow between Collibra and Google Cloud Knowledge Catalog for governed metadata exchange.
• How Dataplex receives outbound governance context and returns inbound discovery signals to the system of record.
• What joint customers can observe in the public preview of the integration inside Google Cloud workflows.
• The live demonstration details presented at Google Cloud Next 2026, including the workflow context shown at the booth.

👉 Read Collibra and Google Cloud's partnership update on bi-directional governance for open lakehouse environments →

Open lakehouse governance: what bi-directional metadata sync changes?

Explore further

View Full Forum →  |  NHI Foundation Course →