Backfills data for a task flow.
Operation description
During a data backfill, task flows are run in sequence based on their dates. You can specify whether task flows are run in chronological or reverse chronological order. After the data backfill is complete, you can specify a date or date range, and a node range to run task flows.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resourcesis used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
| Operation | Access level | Resource type | Condition key | Associated operation |
|---|---|---|---|---|
| dms:BackFill | none | *All Resources * |
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| Tid | long | No | The ID of the tenant. Note
To view the ID of the tenant, go to the Data Management (DMS) console and move the pointer over the profile picture in the upper-right corner. For more information, see View information about the current tenant.
| 3*** |
| DagId | long | Yes | The ID of the task flow. You can call the ListTaskFlow or ListLhTaskFlowAndScenario operation to query the task flow ID. | 15*** |
| StartNodeIds | array | No | The number of nodes for which you want to backfill data. | |
| long | No | The number of task nodes to be replenished. | 2 | |
| FilterNodeIds | array | No | Filter condition, which specifies the list of node IDs in the task flow that do not need to supplement data. | |
| long | No | The ID of the node that does not need to supplement data in the task flow. | 12*** | |
| IsTriggerSubTree | boolean | No | Specifies whether to run descendant nodes. Default value: true. | true |
| BackFillDate | string | No | The date for the data to be backfilled. This parameter is required if you specify a date for data backfill. | 2022-01-14 |
| BackFillDateBegin | string | No | The start date of the date range for the data to be backfilled. This parameter is required if you specify a date range for data backfill. | 2022-01-14 |
| BackFillDateEnd | string | No | The end date of the date range for the data to be backfilled. This parameter is required if you specify a date range for data backfill. | 2022-09-29 |
| Interval | integer | No | The interval at which data backfill is performed. Unit: hours. Minimum value: 1. Default value: 24. | 24 |
| Asc | boolean | No | The running sequence of task flows for data backfill. Valid values:
| 0 |
| HistoryDagId | long | No | The ID of the historical task flow. | 16*** |
The BackFillDate parameter is required if you specify a date for data backfill.
The BackFillDateBegin and BackFillDateEnd parameters are required if you specify a date range for data backfill.
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "7FAD400F-7A5C-4193-8F9A-39D86C4F0231",
"ErrorCode": "UnknownError",
"ErrorMessage": "UnknownError",
"Success": true,
"DagInstanceId": 0,
"NodeId": 0
}Error codes
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|---|---|
| 2023-05-25 | The request parameters of the API has changed. The response structure of the API has changed | View Change Details |