This page has been machine-translated and may contain inaccuracies in phrasing or product terminology. If discrepancies exist, the original Japanese version takes precedence.
This document explains the correspondence between the physical structure of metadata obtained from your organization's data source services and the physical structure of assets in the QDIC catalog. The hierarchical structure and parent-child relationships of metadata differ depending on the data source service, but QDIC defines relationships to absorb differences between services. Correctly understanding the asset structure in the catalog is key to improving asset searchability and is essential for operators to manage assets accurately.
Intended Audience for this Guide
This section explains the relationship between the metadata that shows the data structure of data sources and the assets in the catalog. Assets acquired from data sources and reflected in the catalog have the following hierarchy or parent-child relationships.
- When specifying the asset type in catalog search, please keep in mind the asset structure below.
- When administrators and operators manually create data sources, enter the hierarchical structure of assets to be registered in the CSV file so that it follows the hierarchical structure of each service as shown below.
- Administrators and environment operators should keep in mind that metadata obtained from connectors will be registered in the catalog in the asset hierarchy or parent-child relationship as shown below.
DB Data
- The top-level asset for DB data is Schema.
- If there are data structures higher than Schema on the service side, all of them are treated as Schema. In many services, there is a Database as a data structure higher than Schema, but as an asset this is also a Schema. Therefore, the asset hierarchy display in the catalog is as follows.
Schema 〉Schema 〉Table 〉Column - For the above reason, it is not possible to create rules or conditions such as "Target only Database, exclude Schema" when assigning rule tags or setting custom properties. This is because both are equally considered Schema as assets.
- All objects in the data source are Tables. Views are also treated as Tables.
Amazon Athena
Supported connectors: Metadata Agent
| Metadata | Asset |
|---|---|
| Data Catalog | Schema |
| Database | Schema |
| Table | Table |
| View | Table |
| Column | Column |
Amazon Redshift
Supported connectors: Metadata Agent Intelligence Agent Scanner
| Metadata | Asset |
|---|---|
| Database | Schema |
| Schema | Schema |
| Table | Table |
| View | Table |
| Column | Column |
Azure Data Services (including Microsoft SQL Server)
Supported connectors: Metadata Agent Scanner
| Metadata | Asset |
|---|---|
| Database | Schema |
| Schema | Schema |
| Table | Table |
| View | Table |
| Column | Column |
Databricks
Supported connectors: Metadata Agent Intelligence Agent
| Metadata | Asset |
|---|---|
| Catalog | Schema |
| Schema | Schema |
| Table | Table |
| View | Table |
| Column | Column |
Denodo Virtual DataPort
Supported connectors: Metadata Agent Scanner
| Metadata | Asset |
|---|---|
| Database | Schema |
| View | Table |
| Column | Column |
Google BigQuery
Supported connectors: Metadata Agent Intelligence Agent
| Metadata | Asset |
|---|---|
| Project | Schema |
| Dataset | Schema |
| Table | Table |
| View | Table |
| Column | Column |
Microsoft Fabric Warehouse
Supported connectors: Scanner
| Metadata | Asset |
|---|---|
| Warehouse | Schema |
| Schema | Schema |
| Table | Table |
| View | Table |
| Column | Column |
MySQL
Supported connectors: Metadata Agent
| Metadata | Asset |
|---|---|
| Database | Schema |
| Table | Table |
| View | Table |
| Column | Column |
Oracle Database
Supported connectors: Metadata Agent
| Metadata | Asset |
|---|---|
| Database | Schema |
| Schema (User) | Schema |
| Table | Table |
| View | Table |
| Column | Column |
PostgreSQL
Supported connectors: Metadata Agent
| Metadata | Asset |
|---|---|
| Database | Schema |
| Schema | Schema |
| Table | Table |
| View | Table |
Snowflake
Supported connectors: Metadata Agent Intelligence Agent Scanner
| Metadata | Asset |
|---|---|
| Database | Schema |
| Schema | Schema |
| Table | Table |
| View | Table |
| Column | Column |
Teradata
Supported connectors: Metadata Agent
| Metadata | Asset |
|---|---|
| Database | Schema |
| Table | Table |
| View | Table |
| Column | Column |
Treasure Data
Supported connectors: Metadata Agent
| Metadata | Asset |
|---|---|
| Database | Schema |
| Table | Table |
| Column | Column |
BI Data
- The top-level asset for BI data is BI Group.
- If there are data structures higher than Dashboard on the service side, all of them are treated as BI Group.
- For the above reason, it is not possible to set up tagging or property settings such as "Target only Project, exclude Workbook." This is because both are equally considered BI Group as assets.
- Dashboards have reports or sheets, but all these objects are Sheets.
Microsoft Power BI
Supported connectors: Metadata Agent
| Metadata | Asset |
|---|---|
| Workspace (Group) | BI Group |
| App | BI Group |
| Dashboard | Dashboard |
| Report | Sheet |
Tableau
Supported connectors: Metadata Agent
| Metadata | Asset |
|---|---|
| Project | BI Group |
| Workbook | BI Group |
| Dashboard | Dashboard |
| Sheet | Sheet |
ETL Data
Alteryx
| Metadata | Asset |
|---|---|
| Workflow | ETL |