The entire dataset interface is divided into three modules: 1. Dataset creation, 2. Dataset management, and 3. Dataset list. As shown in the figure below, the green area labeled 2 represents dataset management. In this dataset detail management area, users can perform various operations on the dataset, including data preview, synchronization status, model information, lineage view, row and column permissions, and more. This document provides a detailed explanation of these features.
*For the data readiness configuration of direct connection datasets, see Section 2.10.
Basic dataset information: owner, last synchronization time, dataset size, and access frequency.
The top section supports the following operations:
Supports two preview structures: detailed data and table structure.
Supports editing field information. Click [Edit Field] to enter field information editing mode. For more operation guidelines, see Field Configuration.
Supports searching field names by entering keywords.
Supports previewing target data by specifying filter conditions.
You can view the current status, operation view, and synchronization logs to track specific progress in real time.
Support filtering tasks by specific business date, synchronization status, and data result equal to 0.
Support resynchronizing a single instance and synchronizing data in batches.
Support viewing and modifying detailed synchronization configurations. For more operation instructions, see Synchronization Settings.
View model settings information: model composition, filter criteria, and performance settings. Click the capsule to view specific field information. For more operation instructions, see Model Configuration.
View the usage of the current dataset, including which dashboards it is used in, which charts it is applied to, and statistical information about related resources.
Support downloading lineage information as a file.
Support one-click download of the current table structure information as a file, and allow users to batch modify dimensions/metrics, field names, field expressions, remarks, and more. Support batch addition of new fields.
(1) Click to enter the download page
(2) Download the latest field list
(3) Modify fields in Excel. To add new fields, append them at the bottom of the file
(4) Upload the modified field list and confirm whether the modification is successful. Click Confirm to proceed.
(5) Confirm whether the automatically filled field information is correct. Click Save to take effect.
After selection, a pop-up window will appear, allowing you to make this dataset available for use by other projects. For details, see: Mirror Dataset
Configure the attribution analysis dimensions of the dataset. For details, see: 归因分析配置
Support transferring the owner and alert recipient of the dataset. Caution: When the dataset owner is transferred, the alert owner created based on this dataset will also be transferred synchronously.
By default, only extracted datasets support configuring subscription monitoring push when data synchronization is complete. In the on-premises version, direct connection datasets support monitoring subscription push notifications that are triggered upon data synchronization completion via Data Readiness Configuration.
For a direct connection dataset A, since it does not have synchronization information, it cannot use the monitoring subscription configuration that is triggered upon data synchronization completion. Users can maintain a dataset B that stores the upstream data source readiness configuration information. By configuring the corresponding upstream database table field names and dates in the system, dataset A can be associated with dataset B. This enables the system, in the monitoring subscription scenario, to query dataset B to determine whether all upstream tables used in dataset A are ready.
Steps:
Step 1: Create the "Direct Connection Scenario Data Readiness Information Table" and the "Data Readiness Information Dataset"
(1) Create a new "Direct Connection Scenario Data Readiness Information Table". The following fields are required:
Meaning: Records the database table name and the date when it is ready. The system queries the readiness information table. When it finds that the readiness time for a certain database and table has arrived, it determines that synchronization is complete and triggers monitoring.
Field name | Type | Description |
|---|---|---|
dbName | string | Required |
tableName | string | Required |
partDate | string (2024-01-01) | Required; partition value for data readiness date |
(2) Use the "Direct Connection Scenario Data Readiness Information Table" to create a "Data Readiness Information Dataset", and grant 'View' and higher permissions for the "Data Readiness Information Dataset" to users who need to use this dataset later.
The "Direct Connection Scenario Data Readiness Information Table" and "Data Readiness Information Dataset" are used here for descriptive convenience only; the actual system does not restrict the names of such tables or datasets.
Step 2: Configure readiness information for the direct connection dataset
In the direct connection dataset, under "..." - "More" - "Data Readiness Configuration", confirm the upstream database and table information for the current dataset, and configure the database name, table name, and data readiness date partition from the "Data Readiness Information Dataset" one by one.
Step 3: Support monitoring subscription triggered by the "Data Synchronization Complete" event for direct connection datasets
For users with permission to use direct connection datasets, when using charts and dashboards configured with these datasets in monitoring subscription scenarios, if the system detects that the dataset is configured with "data readiness information", it will support notifications triggered by the "Data Synchronization Complete" event. This prevents downstream users from receiving monitoring subscription notifications before the data is ready.