Manage DLF catalogs - create, view, configure, delete - Data Lake Formation

Prerequisites

Before you begin, make sure that you have:

Set up DLF (one-time activation and authorization)
(RAM users) The AliyunDLFFullAccess permission policy, or a custom policy with catalog-related actions. For more information, see Manage API permissions.
(RAM users) The super_administrator or admin system role, or a custom role with catalog-related data permissions. For more information, see Grant data permissions to a user.

Note

RAM users require both API permissions and data permissions to manage catalogs.

A maximum of 10 catalogs can be created per account in each region. To request an increase, submit a ticket.

Configure the following parameters.

Parameter	Required	Default	Description
Catalog Name	Yes	--	A unique name for the catalog.
Description	No	--	Catalog description.
Storage Type	Yes	Standard Storage	Fixed to Standard Storage.
Storage Redundancy Type	Yes	LRS	Data redundancy policy. Valid values: LRS and ZRS.

Storage Redundancy Type options:

LRS (Locally Redundant Storage): Stores data in a single zone. If the zone becomes unavailable, data is inaccessible. Default option.
ZRS (Zone-Redundant Storage): Replicates data across multiple zones in a region for higher availability.

Important

After a catalog is created, the redundancy type cannot be changed from ZRS to LRS.
ZRS provides higher data availability but incurs higher costs than LRS.

In the left navigation pane, click Catalogs.
Click a catalog name to view its details.
On the Details tab, view basic catalog information.
Click the Permissions tab to grant catalog-level permissions to DLF users or roles. Manage data authorizations.
Click the Storage Optimization tab to configure storage tiering. For more information, see Configure storage optimization.
Click the Catalog Configuration tab to configure file fragment lifecycle and default Paimon table properties. For more information, see Configure catalog settings.

Important

Before you delete a catalog, make sure that the following conditions are met. Otherwise, the deletion fails.

On the Catalogs page, find the target catalog and click Delete in the Actions column.
In the dialog box, click OK.

On the Storage Optimization tab, use Intelligent Tiering to automatically tier hot and cold data across catalog tables by lifecycle rules.

Catalog-level: When enabled, Intelligent Tiering applies to all tables and inherits catalog settings. Table-level overrides remove the "Inherited from Catalog" status.
Table-level: You can enable Intelligent Tiering for individual tables even if catalog-level tiering is disabled.

Strategy	Description
Last Access Time	Triggers rules based on when table or partition data was last accessed.
Last Update Time	Triggers rules based on when table or partition data was last updated.

Configure rules to transition data between storage classes. Minimum storage duration varies by class.

Rule	Default (days)	Description
Transition to Infrequent Access	30	Moves data to Infrequent Access (IA) storage after the specified days. IA data remains accessible by compute engines with reduced performance.
Transition to Archive	60	Moves data to Archive storage after the specified days. Archived data is inaccessible by compute engines.
Transition to Cold Archive	180	Moves data to Cold Archive storage after the specified days. Cold-archived data is inaccessible by compute engines.

The Transition to Infrequent Access and Transition to Archive rules support an additional option:

Convert to Standard Storage Upon Access: Automatically restores the partition or non-partitioned table to Standard storage when accessed.

Note

Convert to Standard Storage Upon Access is available only when Tiering Strategy is set to Last Access Time.

On the Catalog Configuration tab, configure these catalog-level settings.

Set the expiration time for file fragments (minimum: 1 day). Expired fragments are deleted automatically and cannot be recovered.

Override default properties for Paimon tables. Paimon Table.