Changes to metadata stored in Dataplex Universal Catalog

Between January 12, 2026 and February 2, 2026, some of the metadata stored in Dataplex Universal Catalog will change.

This change brings the metadata stored in Dataplex Universal Catalog into consistency with metadata from the original source systems.

If your workloads fall within the scope of changes described in the next section, follow the instructions in this document.

Scope of changes

The changes described in this section apply to entries from the following source systems:

  • Vertex AI
  • Bigtable
  • Spanner
  • Pub/Sub
  • Dataform
  • Dataproc Metastore

The following Dataplex API methods are affected by these changes:

Resource names

The resource name changes for the top-level entry field entrySource.resource. The field is modified to contain a relative resource name instead of the full resource name with the API. The //<service_name>.googleapis.com/ prefix is removed from the resource name. The following table lists some sample examples.

Source system Value before the change Value after the change
Vertex AI //aiplatform.googleapis.com/projects/PROJECT_ID/locations/LOCATION_ID/featureOnlineStores/REMAINING_PATH
Example: //aiplatform.googleapis.com/projects/test-project-id/locations/us-central1/featureOnlineStores/test-store		 projects/PROJECT_ID/locations/LOCATION_ID/featureOnlineStores/REMAINING_PATH
Example: projects/test-project-id/locations/us-central1/featureOnlineStores/test-store
Bigtable //bigtable.googleapis.com/projects/PROJECT_ID/instances/INSTANCE_ID/tables/TABLE_ID
Example: //bigtable.googleapis.com/projects/test-project-id/instances/test-instance/tables/test-table		 projects/PROJECT_ID/instances/INSTANCE_ID/tables/TABLE_ID
Example: projects/test-project-id/instances/test-instance/tables/test-table
Spanner //spanner.googleapis.com/projects/PROJECT_ID/instances/INSTANCE_ID/databases/DATABASE_ID
Example: //spanner.googleapis.com/projects/test-project-id/instances/test-instance/databases/test-database		 projects/PROJECT_ID/instances/INSTANCE_ID/databases/DATABASE_ID
Example: projects/test-project-id/instances/test-instance/databases/test-database
Pub/Sub //pubsub.googleapis.com/projects/PROJECT_ID/topics/TOPIC_ID
Example: //pubsub.googleapis.com/projects/test-project-id/topics/test-topic		 projects/PROJECT_ID/topics/TOPIC_ID
Example: projects/test-project-id/topics/test-topic
Dataform //dataform.googleapis.com/projects/PROJECT_ID/locations/LOCATION_ID/repositories/REPOSITORY_ID
Example: //dataform.googleapis.com/projects/test-project-id/locations/us-central1/repositories/test-repo		 projects/PROJECT_ID/locations/LOCATION_ID/repositories/REPOSITORY_ID
Example: projects/test-project-id/locations/us-central1/repositories/test-repo
Dataproc Metastore //metastore.googleapis.com/projects/PROJECT_ID/locations/LOCATION_ID/services/SERVICE_ID
Example: //metastore.googleapis.com/projects/test-project-id/locations/us-central1/services/test-service		 projects/PROJECT_ID/locations/LOCATION_ID/services/SERVICE_ID
Example: projects/test-project-id/locations/us-central1/services/test-service

For more information about this field, see the EntrySource API reference.

Ancestor type values

The top-level entry field entrySource.ancestors.type changes to contain the Dataplex type project ID (dataplex-types) instead of the Dataplex type project number (655216118709). The following table lists some sample examples.

Source system Value before the change Value after the change
Vertex AI DATAPLEX_TYPE_PROJECT_NUMBER.global.vertexai-feature-online-store
Example: 655216118709.global.vertexai-feature-online-store		 DATAPLEX_TYPE_PROJECT_ID.global.vertexai-feature-online-store
Example: dataplex-types.global.vertexai-feature-online-store
Dataproc Metastore DATAPLEX_TYPE_PROJECT_NUMBER.global.DataprocMetastoreDatabase
Example: 655216118709.global.DataprocMetastoreDatabase		 DATAPLEX_TYPE_PROJECT_ID.global.dataproc-metastore-database
Example: dataplex-types.global.dataproc-metastore-database
Spanner DATAPLEX_TYPE_PROJECT_NUMBER.global.cloud-spanner-instance
Example: 655216118709.global.cloud-spanner-instance		 DATAPLEX_TYPE_PROJECT_ID.global.cloud-spanner-instance
Example: dataplex-types.global.cloud-spanner-instance
Bigtable DATAPLEX_TYPE_PROJECT_NUMBER.global.cloud-bigtable-instance
Example: 655216118709.global.cloud-bigtable-instance		 DATAPLEX_TYPE_PROJECT_ID.global.cloud-bigtable-instance
Example: dataplex-types.global.cloud-bigtable-instance

For more information about this field, see the Ancestor API reference.

What you need to do

The rollout period starts on January 12, 2026 and ends on February 2, 2026. The changes to the metadata apply gradually throughout the rollout period.

Here's what you need to do:

  • Before January 12, 2026, update your workloads to interpret both the legacy version of metadata and the updated version of metadata.

  • During the rollout period, entries might capture the legacy version of metadata or the updated version of metadata. Your workloads must be able to interpret both versions.

  • After February 2, 2026, optionally update your workloads to interpret only the new version of metadata.

How to determine metadata version

To determine whether an entry uses the updated metadata, look for the entry's aspects object and locate the relevant aspect type. In the aspect type's aspectSource object, if the dataVersion field is present and set to Ingestion/1.0.0, the entry uses the updated metadata version. For more information, see the lookupEntry and getAspectType APIs.

Support

For questions, contact dataplex-msa-support@google.com.

Additional information