A logical dimension table for enumeration is used to list and standardize enumeration values to identify enumeration dimension objects, such as a k-v structured code table for gender. This topic describes how to create and configure a logical dimension table for enumeration.
Prerequisites
The creation of the enumeration business object is completed. For more information, see create and manage business entities.
Procedure
Step 1: Create a Logical Dimension Table for Enumeration
In the top menu bar of the Dataphin home page, select Development > Data Development.
In the top menu bar, select Project (Dev-Prod mode also requires selecting Environment).
In the left-side navigation pane, select Standard Modeling > Logical Dimension Table.
In the logical dimension table list on the right, click
the new icon.
In the New Logical Dimension Table dialog box, configure the following parameters.
Parameter
Description
Business Object
Select enumeration object.
Table Type
The business object selects enumeration object. The table type is logical dimension table for enumeration and cannot be modified.
Data Section
Defaults to the data section associated with the project and cannot be modified.
Subject Area
Supports selecting all subject areas under the data section.
Compute Engine
Set the Dataphin instance to support the selection of compute engines, including Hive, Impala, and Spark, for tenants of the Hadoop compute engine.
ImportantThe corresponding compute engine needs to be enabled before it can be selected. For more information, see create a Hadoop compute source.
When the compute engine is TDH 6.x or TDH 9.3.x, configuration is not supported for this item.
The compute engine has the following limitations:
Hive: Cannot read source tables stored in Kudu format.
Impala: Can read source tables stored in Kudu format but does not currently support storing logical tables in Kudu. If there are no source tables in Kudu format, it is not recommended to use.
Spark: Spark cannot read source tables stored in Kudu format.
Data Timeliness
Data timeliness is used to define the scheduling type of subsequent logical dimension table tasks in the production environment. The data timeliness of a logical dimension table for enumeration defaults to T+1 (daily task).
Logical Table Name
Dataphin automatically fills in the logical table name. The naming convention is
<data section name>.dim_enum_custom name
.The naming conventions for custom names are as follows:
Allows letters, numbers, or underscores (_).
Can be up to 100 characters in length.
Chinese Name
The naming conventions are as follows:
Can be up to 128 characters in length.
Supports any character.
Description
Provide a brief description of the logical dimension table for enumeration, within 1000 characters.
Click Next.
Step 2: Configure Enumeration Values for the Logical Dimension Table
In the Logical Dimension Table Calculation Logic dialog box, configure the enumeration values for the logical dimension table.
Enumeration Values: The structure of enumeration values is a Key-Value code table, with a comma (,) separating the Key and Value. An example is as follows:
F,Female M,Male
Click OK.
Step 4: Save and Submit the Logical Table
In the current logical dimension table tab, click Submit. After filling in the Remarks, click Confirm And Submit.
What to do next
In a Dev-Prod project mode, you must publish the logical table to the production environment. For detailed instructions, see manage publishing tasks .
Once the logical table has been deployed to the production environment, you can manage and monitor logical table tasks within the Operation Center. For detailed instructions, see Scheduling center.