Data Flow Supports Importing Smart ETL

1. Overview

To support users' smooth transition from Smart ETL to using data development functionality, data development supports one-click Smart ETL migration. This feature can quickly and completely migrate your created ETLs (including task configurations, operator dependencies, and datasets used) to the new platform, achieving seamless business continuity.

2. Operation Steps

1. Enter the data development module, select the folder for creating offline development tasks, and create a new offline development task.

   

2. Drag in the data flow node, double-click or click edit to enter the data flow development page.

   

3. Click "..." > "Smart ETL Import" in the upper right corner. A popup will display ETLs that the task owner has at least usage permissions for. Select the ETL that needs to be migrated.

   Note

   After ETL migration, all current data flow nodes and configurations will be overwritten.

   

4. After completion, all nodes in the data flow (including operator configurations, operator dependencies, and input datasets) will be migrated. Output datasets need to be created again or select existing datasets (only offline development datasets are supported).

   

   Output datasets support full and incremental updates. When the data structure of predecessor nodes changes, automatic data structure updates are supported, automatically adding fields to existing tables.

   

5. The ETL dataset A output before migration may be used as the input dataset for subsequent Smart ETLs. After migration, data is input to offline development dataset B, and ETL dataset A will no longer receive data. One-click switching functionality is supported to switch the input dataset of subsequent ETLs from A to B.

   

   Select the offline development dataset to switch to

   

   Check if there are any missing fields, and click OK if there are no errors to complete the migration

   

   It is recommended to perform dataset switching for subsequent ETLs before migration to reduce manual operation steps.

6. The original output ETL dataset A may have been used to create cards. After migration, it is replaced with offline development dataset B. One-click switching of datasets used by cards to offline development dataset B is supported.

   Supports batch creation or one-click switching of all cards.

   

   Select the offline development dataset to switch to.

   

   Check if there are any missing fields, and click OK if there are no errors to complete the migration.

   

7. Scheduling configuration: After all ETLs complete migration, reconfigure scheduling. Offline development configures event scheduling for all initial data flow input datasets.