Question

A retail analytics team publishes an Analytics Hub listing so that a partner organization can consume a curated BigQuery dataset. After the partner subscribes to the linked dataset in their own project, an analyst on the partner side reports that they can query the shared tables but cannot see any newly added tables that the publisher created in the source dataset last week. The publisher confirms the new tables exist and are populated. What is the most likely cause and correct resolution?

Accepted Answer

Analytics Hub linked datasets only reflect tables present when the listing was created; the publisher must republish or refresh the listing so newly added tables are included in the shared dataset.

Answer

The partner's linked dataset caches results for 7 days; the analyst must wait for the cache to expire before the new tables appear.

Answer

The new tables are automatically part of the linked dataset, but the partner analyst lacks bigquery.tables.get on them, so the publisher must grant the analyst column-level IAM on each new table.

Answer

Linked datasets cannot include tables added after subscription; the publisher must delete and recreate the entire listing, and the partner must resubscribe each time schema changes.