The OpenLake Data Catalog is a workspace-level metadata workbench that facilitates quick access for data developers. It centralizes metadata from sources such as MaxCompute, Hologres, and DLF, and supports the following capabilities:
Unified Management: Centralizes management of tables, views, functions, and resources across multiple data sources.
Quick Exploration: Previews table structures for quick data insights.
Supported Data Catalogs
The following table lists supported data sources and addition methods.
Data Catalog | Workspace-bound Data Sources | Account-level Data Sources |
MaxCompute (Internal Project, External Project) | ||
Hologres (Internal Database, External Database) | ||
DLF Catalog (DLF 1.0, 2.0, 2.5 and later) | ||
Hive (EMR Hive) | ||
Lindorm | ||
AnalyticDB for MySQL | ||
AnalyticDB for PostgreSQL | ||
StarRocks | ||
AI Catalog (AI Datasets, AI Models) | The system reads data from the AI workspace with the same name as the current DataWorks workspace. |
Authentication and Authorization
Metadata read access depends on the data source addition method:
For workspace-bound instances, the Data Catalog reads data using the **identity configured for the data source**.
For account-level instances, the Data Catalog uses your **personal identity** (current login account).
To view MaxCompute data as a RAM User or RAM Role, you must obtain the required MaxCompute permissions. If the MaxCompute source uses the three-layer model, you must also grant the RAM User or RAM Role permission to view Schema metadata.
NoteIf a MaxCompute project contains multiple schemas, grant metadata permissions for all schemas to view the complete list on the project details page.
Grant permissions to a RAM User:
GRANT DESCRIBE ON SCHEMA <Schema_Name> TO USER RAM$<Account_Name>:<RAM_User_Name>;Grant permissions to a RAM Role:
GRANT DESCRIBE ON SCHEMA <Schema_Name> TO USER `RAM$<Account_Name>:role/<RAM_Role_Name>`;
Access the Data Catalog
You can access the workspace Data Catalog only when the workspace mode is OpenLake.
Log on to the DataWorks Workspace List Page. Select the region. Find the workspace and click Management > Data Catalog in the Actions column to access the workspace Data Catalog.
Add a Data Catalog
Build a shared workspace-level directory tree as follows:
Find the data source type and click the
icon next to its name.Find the instance or data source and click Add in the Actions column.
Catalogs added from workspace-bound data sources are visible to workspace members.
Catalogs added from account-level data sources are visible only to you.
For account-level sources, the list displays only instances in the same region as the DataWorks workspace that you have permission to access.
Manage Data Catalogs
Remove a Data Catalog
To remove an unneeded data catalog:
In the directory tree, find the catalog. Click Remove or Unbind Data Catalog in the Actions column.
Create and Manage Data Objects
Expand a catalog in the directory tree to create or manage data objects. See the table below for details.
Data Catalog | Description | Related Documentation |
MaxCompute | Create and manage objects like tables, views, external tables, resources, and functions. | |
Hologres | Create and manage data objects such as tables and views. | |
DLF Catalog | Create and manage database table metadata. | |
Hive | Create and manage table data objects. | |
AnalyticDB for MySQL | Create and manage table data objects. | |
AnalyticDB for PostgreSQL | Create and manage table data objects. | |
StarRocks | Create and manage data objects such as tables and views. | |
AI Catalog | Manage AI Catalog datasets and model metadata. |
FAQ
Q: What is the difference between the workspace Data Catalog and the Data Development catalog?
A: Administrators initialize the workspace Data Catalog for all developers. In Data Development, users can build personalized data catalogs based on the workspace Data Catalog.