DataWorks:UpdateDIJob

Each rule can select different object types from the source, such as source databases and source tables.

The transformation rules applied to source objects.

A single column type mapping.

The scheduling parameters.

A single DDL handling setting.

The runtime settings.

The CUs of the resource group for Data Integration used for batch synchronization.

The name of the resource group for Data Integration that are used for batch synchronization.

The CUs of the resource group for Data Integration that are used for real-time synchronization.

The name of the resource group for Data Integration that are used for real-time synchronization.

The CUs of the scheduling resource group for batch synchronization tasks.

The name of the scheduling resource group used for batch synchronization tasks.

Valid values:

• DefinePrimaryKey
• Rename
• AddColumn
• HandleDml
• DefineIncrementalCondition
• DefineCycleScheduleSettings
• DefinePartitionKey

The rule expression in JSON string format.

1. Rename rule

• Example: {"expression":"${srcDatasourceName}_${srcDatabaseName}_0922" }
• expression: The rename transformation expression. Supported variables include: ${srcDatasourceName} (source data source name), ${srcDatabaseName} (source database name), and ${srcTableName} (source table name).

2. AddColumn rule

• Example: {"columns":[{"columnName":"my_add_column","columnValueType":"Constant","columnValue":"123"}]}
• If not specified, the default behavior is to not add columns.
• columnName: The name of the column to add.
• columnValueType: The value type of the column to add. Valid values: Constant and Variable.
• columnValue: The value of the column to add. When columnValueType is set to Constant, the value is a custom constant of the string type. When columnValueType is set to Variable, the value is a built-in variable. Built-in variables include: EXECUTE_TIME (execution time, long type), DB_NAME_SRC (source database name, string type), DATASOURCE_NAME_SRC (source data source name, string type), TABLE_NAME_SRC (source table name, string type), DB_NAME_DEST (destination database name, string type), DATASOURCE_NAME_DEST (destination data source name, string type), TABLE_NAME_DEST (destination table name, string type), and DB_NAME_SRC_TRANSED (transformed source database name, string type).

3. DefinePrimaryKey

• Example: {"columns":["ukcolumn1","ukcolumn2"]}
• If not specified, the source primary key columns are used by default.
• When the destination table already exists: Data Integration does not modify the destination table structure. If the specified primary key columns are not in the destination table, the task fails to start.
• When the destination table is auto-created: Data Integration automatically creates the destination table structure with the defined primary key columns. If the specified primary key columns are not in the destination table, the task fails to start.

4. HandleDml rule

• Example of a rule used to process DML messages: {"dmlPolicies":[{"dmlType":"Delete","dmlAction":"Filter","filterCondition":"id > 1"}]}.
• If not specified, the default rule is Normal for Insert, Update, and Delete.
• dmlType: The DML operation type. Valid values: Insert, Update, Delete.
• dmlAction: The DML handling policy. Valid values: Normal, Ignore, Filter (conditional processing, used when dmlType is Update or Delete), and LogicalDelete.
• filterCondition: The DML filter condition. This parameter is used when dmlAction is set to Filter.

5. DefineIncrementalCondition

• Example: {"where":"id > 0"}
• Specifies the incremental filter condition.

6. DefineCycleScheduleSettings

• Example: {"cronExpress":" * * * * * *", "cycleType":"1"}
• Specifies the scheduled task parameters.

7. DefinePartitionKey

• Example: {"columns":["id"]}
• Specifies the partition key.

The rule name. When the action type and target type are the same, the rule name must be unique. The name cannot exceed 50 characters.

The target type for the action. Valid values:

• Table
• Schema
• Database