The ID of the workspace.
Debugging
Authorization information
There is currently no authorization information disclosed in the API.
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
Owner | string | No | The description of the node. | 193379**** |
BizName | string | No | The error code returned. | test_bizName |
ProgramType | string | No | The operation that you want to perform. Set the value to ListNodes. | ODPS_SQL |
PageNumber | integer | No | The number of entries to return on each page. Default value: 10. Maximum value: 100. | 1 |
PageSize | integer | No | The ID of the workspace. | 10 |
ProjectId | long | Yes | The ID of the owner. | 1234 |
ProjectEnv | string | Yes | The number of entries returned per page. Default value: 10. Maximum value: 100. Enumeration Value:
| PROD |
NodeName | string | No | The ID of the baseline with which the node is associated. | liux_test_n**** |
Response parameters
Examples
Sample success responses
JSON
format
{
"HttpStatusCode": 200,
"RequestId": "E6F0DBDD-5AD****",
"ErrorMessage": "The connection does not exist.",
"ErrorCode": "Invalid.Tenant.ConnectionNotExists",
"Success": true,
"Data": {
"PageNumber": 1,
"PageSize": 10,
"TotalCount": 66,
"Nodes": [
{
"SchedulerType": "NORMAL",
"RepeatInterval": 60,
"Repeatability": true,
"ProjectId": 33671,
"ProgramType": "ODPS_SQL",
"Priority": 1,
"OwnerId": "19337906836551",
"Connection": "odps_first",
"ParamValues": "a=b",
"RelatedFlowId": 1231123,
"DqcType": 1,
"BaselineId": 123456,
"Description": "test",
"NodeName": "liux_test_n****",
"ResGroupName": "The ID of the request. You can use the ID to query logs and troubleshoot issues.\n",
"BusinessId": 123,
"DqcDescription": "[{\"projectName\":\"ztjy_dim\",\"tableName\":\"dim_user_agent_manage_area_a\",\"partition\":\"ds\\u003d$[yyyy-mm-dd-1]\"}]",
"CronExpress": "00 00 00 * * ?",
"NodeId": 1234,
"ResGroupIdentifier": "",
"FileType": 0
}
]
}
}
Error codes
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2024-05-30 | The response structure of the API has changed | View Change Details |
2023-06-25 | The internal configuration of the API is changed, but the call is not affected | View Change Details |