After the synchronization, assets become available in Collibra.
If no domain mappings are provided, the assets are created in the same domain as the System asset.
Warning Do not move the assets to another domain. Doing so may lead to errors during future synchronizations.
Tip Google Dataplex Catalog synchronization relies on UUIDs.
By default, the assets get the Implemented status.
Edge naming conventions for created assets during the Dataplex Catalog ingestion
The assets created when integrating Dataplex Catalog receive a unique full name (fully qualifying name) based on the following naming convention:
| Asset type | Naming convention | Example |
|---|---|---|
| Schema | systemAssetName>DatabaseName>SchemaName | BigQuery>catalog-integrations>pedro_es_dataset |
| Table | systemAssetName>DatabaseName>SchemaName>tableName | BigQuery>catalog-integrations>pedro_es_dataset>shop |
| Column | systemAssetName>DatabaseName>SchemaName>tableName>columnName(column) | BigQuery>catalog-integrations>pedro_es_dataset>shop>location(column) |
Synchronized metadata for Dataplex Catalog ingestion
This table shows the metadata for each Google Dataplex Catalog asset type if you selected the Dataplex Catalog ingestion. If you do not see any of the listed synchronized metadata, you can add characteristics to the layout on the asset type page.
| Asset type | Synchronized metadata | Resource ID |
|---|---|---|
| Database | ||
| Schema | Description from source system | 00000000-0000-0000-0001-000500000074 |
| Table | Description from source system | 00000000-0000-0000-0001-000500000074 |
|
Schema contains / is part of Table |
00000000-0000-0000-0001-002700000002 | |
| Column |
Technical Data Type |
00000000-0000-0000-0000-000000000219 |
|
Column Position |
00000000-0000-0000-0001-000500000020 | |
|
Is Nullable |
00000000-0000-0000-0001-000500000011 | |
|
Column is part of / contains Table |
00000000-0000-0000-0000-000000007042 | |
| Description from source system | 00000000-0000-0000-0001-000500000074 |