Generates the JSON for an asynchronous thread that is used to update a real-time synchronization task in Data Integration.
Operation description
DataWorks allows you to use only the UpdateDISyncTask operation to update a batch synchronization task in Data Integration. To update a real-time synchronization task, you must first call the GenerateDISyncTaskConfigForUpdating operation to generate the ID of an asynchronous thread and call the QueryDISyncTaskConfigProcessResult operation to obtain the asynchronously generated parameters based on the ID. Then, you can call the UpdateDISyncTask operation and use the parameters as request parameters to update a real-time synchronization task in Data Integration. DataWorks allows you to create or update real-time synchronization tasks in Data Integration only in asynchronous mode.
Debugging
Authorization information
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
ProjectId | long | Yes | The DataWorks workspace ID. You can log on to the DataWorks console and go to the Workspace page to obtain the workspace ID. You must configure this parameter to specify the DataWorks workspace to which the API operation is applied. | 10000 |
TaskType | string | Yes | The type of the object that you want to update in Data Integration in asynchronous mode. Valid values:
Valid values:
| DI_REALTIME |
TaskParam | string | Yes | The script for updating the real-time synchronization task in Data Integration. DataWorks allows you to add or remove tables for a real-time synchronization task in Data Integration only in asynchronous mode. The following types of real-time synchronization tasks are supported:
The SelectedTables parameter is used to specify tables that you want to synchronize from multiple databases. The Tables parameter is used to specify tables that you want to synchronize from a single database.
| { "steps": [ { "parameter": { "connection": [ { "table": [ "xyx" ] } ] }, "name": "Reader", "category": "reader" } ] } |
ClientToken | string | No | The client token that is used to ensure the idempotence of the request. This parameter is used to prevent repeated operations that are caused by multiple calls. | ABFUOEUOTRTRJKE |
TaskId | long | Yes | The task ID.
| 100 |
Response parameters
Examples
Sample success responses
JSON
format
{
"Success": true,
"RequestId": "0bc1411515937635973****",
"Data": {
"Status": "true",
"ProcessId": 10,
"Message": "XXX is invalid."
}
}
Error codes
HTTP status code | Error code | Error message |
---|---|---|
400 | Invalid.DI.Parameter | The parameter is invalid. |
400 | Invalid.DI.Parameter.File.Existed | The file name already exists. |
403 | Forbidden.DI.NoPrivilege | No access. |
500 | InternalError.DI.Parameter | A DI internal error occurred. |
For a list of error codes, visit the Service error codes.