Synchronizing DDL Changes Using Scheduled Pipeline

  • Last update: June 09, 2026
  • Overview

    Version

    FineDataLink VersionFunctional Change
    4.2.12.4

    Supported DDL event detection for Scheduled Pipeline.

    Supported Synchronize Source Table Structure Change for Scheduled Pipeline, enabling synchronization of changes such as new fields and data type changes.

    Application Scenario

    When a scheduled pipeline task synchronizes data from application data sources, the source table structure may undergo DDL changes due to business adjustments (such as adding/deleting tables/fields). If these changes are not detected and handled promptly, synchronization errors and data inconsistencies may occur, affecting downstream business operations.

    You want to detect these changes quickly and have the flexibility to manually update mappings or automatically synchronize certain DDL changes.

    Function Description

    Source DDL change detection: If the source table or its structure changes, the task details page displays the corresponding change information.

    Synchronize Source Table Structure Change: For supported source types, if Synchronize Source Table Structure Change is enabled, DDL changes are automatically synchronized during task execution, requiring no manual updates to field mappings.

    Detectable Source Table Structure Changes and Handling Methods

    The following table lists the detectable changes to source tables and source table structures and handling methods:

    Change TypeManual UpdateAutomatic Synchronization
    Table count and table name changesSource tables are added.Manual table adding is required.Automatic synchronization is not supported.
    Source tables are deleted.Manual table deletion is required.
    Source tables are renamed.Table renaming is treated as table deletion.
    You must remove the tables from the task manually and then
    re-add them.
    Source table structure changeSource fields are added.Manual mapping updates are supported.
    For details, see the "Manual Update" section of this document.
    Changes are synchronized automatically if Synchronize Source Table Structure Change is enabled.
    For details, see the "Automatic Synchronization" section of this document.
    Source fields are deleted.
    Source fields are renamed.
    Data types of source fields are modified.
    Source-end primary key fields are modified.Editing source-end primary keys is not supported in Field Mapping. You must delete tables and re-add them.Automatic synchronization is not supported.

    Manual Update

    On the task details page, if the source table structure has changed, the prompt "The mapping of x table(s) can be updated." will be displayed. You can click Filter to list tables with updatable mappings, as shown in the following figure.

    Click the  icon to enter the editing page, as shown in the following figure.

    Updating Field Mappings

    If the source table structure has changed, click Update Mapping to update the source table structure, as shown in the following figure.

    The Update Mapping table displays the changes in source fields. Click Update Mapping and Target Table to enter the Update Target Table dialog. For details about updating the target table, see the "Updating the Target Table" section of this document.


    After you click Update Mapping, the system first updates the field mappings of the source table and highlights the conflict content in the target table in red in Field Mapping. You need to click the Update Target Table button to adjust the target table. For details about updating the target table, see the "Updating the Target Table" section of this document.

    Updating the Target Table

    If the source field has changed, you can modify the field mapping by selecting the existing fields or manually adding fields. After you confirm the changes in the mapping relationships, the DDL statement for the target table is generated and executed.

    • You can create, delete, and rename fields in the target table.

    • You can modify the data type, length, and precision of fields in the target table.

    • You can configure Not Null, Primary Key, and Remark for the target table.

    • Change records are displayed. You can revert changes.

    1. Click Update Target Table. The popup displays the actual fields of the target table in order. You can adjust the field structure, as shown in the following figure.

    2. You can use the one-click apply function. The field name is used as the unique identifier (based on the Map Fields with Same Name logic) to compare the structures of the source and target tables. If any inconsistencies are detected, you can synchronize the source table structure changes to the target table with one click.

    The following table describes the change records.

    Change RecordDescription
    AddedFields that exist in the source table but not in the target table are marked as Added.
    ModifiedFields with the same name exist in the target table, but the Type, Remark, Primary Key, or Not Null properties differ from those in the source table.
    iconNote:
    Remark, Primary Key, and Not Null settings can be applied if they can be obtained from the source table. Existing values of the target table are preserved otherwise.
    DeletedFields that exist in the target table but not in the source table are marked as Deleted.

    iconNote:
    If you click Apply and then make changes on this page that cause the source table and target table structures to become inconsistent, the Apply-related prompt will not appear again.

    3. Update statements are generated based on the update content. Click Execute Update Statement, as shown in the following figure.

    Automatic Synchronization

    For certain source table structure changes, you can enable Synchronize Source Table Structure Change, which ensures automatic change synchronization during task execution without the need for manual mapping updates, as shown in the following figure.

    The following table describes the change synchronization effects in various scenarios with this function enabled.

    Source Table TypeChange TypeAutomatic Processing -
    Target Table Structure
    Automatic Processing -
    Mapping
    Automatic Processing -
    Target Table Data
    Incremental table with a primary keySource fields are added.Columns are added to the target table.New fields are mapped automatically.In the new columns, values of historical data are NULL, and values of newly written data are the new field values.
    To refresh historical data, manual resynchronization is required.
    Source fields are deleted.The structure remains unchanged.The source fields are deleted in Field Mapping.In the columns of deleted fields, values of historical data remain unchanged, and values of newly written data are NULL.
    To refresh historical data, manual resynchronization is required.
    Source fields are renamedRenaming a field is treated as deleting the old field and creating a new one.
    Data types of source-end fields are modified.The data type of the corresponding field in the target table is modified. Modification failure will be logged without affecting task execution.Field data types on both sides of the mapping are modified. If the modification fails, only the data type of the source field will be modified.Normally, both historical and newly written data have values in the corresponding columns.
    If modification fails, new data will still be written to the corresponding columns. If the data type is not supported for writing, the data will be recorded as dirty data.
    Source-end primary key fields are modified.No action is taken. The task fails. The table must be reconfigured.
    Full table with a primary keyThe table structure changes.The target table structure is changed to match the source table structure.Mappings are refreshed based on the new structure.Data is written after table emptying. There is no historical data.
    Full table without a primary keyThe table structure changes.The target table structure is changed to match the source table structure.Mappings are refreshed based on the new structure.Data is written after table emptying. There is no historical data.

    Viewing the Log

    After the task runs, you can view the execution logs in Execution Record to check source table structure changes, as shown in the following figure.

    附件列表


    主题: Scheduled Pipeline
    • Helpful
    • Not helpful
    • Only read

    滑鼠選中內容,快速回饋問題

    滑鼠選中存在疑惑的內容,即可快速回饋問題,我們將會跟進處理。

    不再提示

    10s後關閉

    Get
    Help
    Online Support
    Professional technical support is provided to quickly help you solve problems.
    Online support is available from 9:00-12:00 and 13:30-17:30 on weekdays.
    Page Feedback
    You can provide suggestions and feedback for the current web page.
    Pre-Sales Consultation
    Business Consultation
    Business: international@fanruan.com
    Support: support@fanruan.com
    Page Feedback
    *Problem Type
    Cannot be empty
    Problem Description
    0/1000
    Cannot be empty

    Submitted successfully

    Network busy