DataWorks:GetDIJob

The name of the data source.

The data type mapping between a source field and a destination field.

The synchronization type that requires periodic scheduling. Valid values:

• Full: full synchronization
• OfflineIncremental: batch incremental synchronization

The scheduling parameters.

The type of the DDL operation. Valid values:

• RenameColumn
• ModifyColumn
• CreateTable
• TruncateTable
• DropTable
• DropColumn
• AddColumn

The runtime setting.

The number of compute units (CUs) in the resource group for scheduling that are used for batch synchronization.

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

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

The identifier of the resource group for Data Integration used for real-time synchronization.

The number of CUs in the resource group for Data Integration that are used for scheduling.

The identifier of the resource group for scheduling used by the synchronization task.

The name of the data source.

The properties of the data source.

The list of rules used to select synchronization objects in the source.

The list of transformation rules that are applied to the synchronization objects selected from the source. Each entry in the list defines a transformation rule.

The action type. Valid values:

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

The expression of the rule. The expression is a JSON string.

1. Example of a renaming rule

• Example: {"expression":"${srcDatasourceName}_${srcDatabaseName}_0922" }
• expression: the expression of the renaming rule. You can use the following variables in an expression: ${srcDatasourceName}, ${srcDatabaseName}, and ${srcTableName}. ${srcDatasourceName} indicates the name of the source. ${srcDatabaseName} indicates the name of a source database. ${srcTableName} indicates the name of a source table.

2. Example of a column addition rule

• Example: {"columns":[{"columnName":"my_add_column","columnValueType":"Constant","columnValue":"123"}]}
• If no rule of this type is configured, no fields are added to the destination and no values are assigned by default.
• columnName: the name of the field that is added.
• columnValueType: the value type of the field. Valid values: Constant and Variable.
• columnValue: the value of the field. If the columnValueType parameter is set to Constant, the value of the columnValue parameter is a constant of the STRING data type. If the columnValueType parameter is set to Variable, the value of the columnValue parameter is a built-in variable. The following built-in variables are supported: EXECUTE_TIME (LONG data type), DB_NAME_SRC (STRING data type), DATASOURCE_NAME_SRC (STRING data type), TABLE_NAME_SRC (STRING data type), DB_NAME_DEST (STRING data type), DATASOURCE_NAME_DEST (STRING data type), TABLE_NAME_DEST (STRING data type), and DB_NAME_SRC_TRANSED (STRING data type). EXECUTE_TIME indicates the execution time. DB_NAME_SRC indicates the name of a source database. DATASOURCE_NAME_SRC indicates the name of the source. TABLE_NAME_SRC indicates the name of a source table. DB_NAME_DEST indicates the name of a destination database. DATASOURCE_NAME_DEST indicates the name of the destination. TABLE_NAME_DEST indicates the name of a destination table. DB_NAME_SRC_TRANSED indicates the database name obtained after a transformation.

3. Example of a rule used to specify primary key fields for a destination table

• Example: {"columns":["ukcolumn1","ukcolumn2"]}
• If no rule of this type is configured, the primary key fields in the mapped source table are used for the destination table by default.
• If the destination table is an existing table, Data Integration does not modify the schema of the destination table. If the specified primary key fields do not exist in the destination table, an error is reported when the synchronization task starts to run.
• If the destination table is automatically created by the system, Data Integration automatically creates the schema of the destination table. The schema contains the primary key fields that you specify. If the specified primary key fields do not exist in the destination table, an error is reported when the synchronization task starts to run.

4. Example of a rule used to process DML messages

• Example: {"dmlPolicies":[{"dmlType":"Delete","dmlAction":"Filter","filterCondition":"id > 1"}]}
• If no rule of this type is configured, the default processing policy for messages generated for insert, update, and delete operations is Normal.
• dmlType: the DML operation. Valid values: Insert, Update, and Delete.
• dmlAction: the processing policy for DML messages. Valid values: Normal, Ignore, Filter, and LogicalDelete. Filter indicates conditional processing. The value Filter is returned for the dmlAction parameter only when the value of the dmlType parameter is Update or Delete.
• filterCondition: the condition used to filter DML messages. This parameter is returned only when the value of the dmlAction parameter is Filter.

5. Example of a rule used to perform incremental synchronization

• Example: {"where":"id > 0"}
• The rule used to perform incremental synchronization is returned.

6. Example of a rule used to configure scheduling parameters for an auto triggered task

• Example: {"cronExpress":" * * * * * *", "cycleType":"1"}
• The rule used to configure scheduling parameters for an auto triggered task is returned.

7. Example of a rule used to specify a partition key

• Example: {"columns":["id"]}
• The rule used to specify a partition key is returned.

The name of the rule. If the values of the RuleActionType parameter and the RuleTargetType parameter are the same for multiple transformation rules, you must make sure that the transformation rule names are unique.

The type of the object on which the action is performed. Valid values:

• Table
• Schema
• Database