ListNodesByOutput - DataWorks - Alibaba Cloud Documentation Center

Queries nodes based on the output of the nodes.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Debug

Authorization information

There is currently no authorization information disclosed in the API.

Request parameters

Parameter	Type	Required	Description	Example
ProjectEnv	string	Yes	The environment of Operation Center. Valid values: PROD and DEV. The value PROD indicates the production environment, and the value DEV indicates the development environment.	PROD
Outputs	string	Yes	The output name of the node. You can specify multiple output names. Separate them with commas (,).	aaaaa.1231412_out,bbbb.12313123_out

Response parameters

Parameter	Type	Description	Example
	object
HttpStatusCode	integer	The HTTP status code.	200
RequestId	string	The request ID.	SDFSDFSDF-asdfDFSDF-SDFSDf-SDfSFD
ErrorMessage	string	The error message.	The connection does not exist.
ErrorCode	string	The error code.	Invalid.Tenant.ConnectionNotExists
Success	boolean	Indicates whether the request was successful.	true
Data	array<object>	The nodes returned.
OutputNodePair	object
Output	string	The output name of the current node.	test_0709_1.630003556_out
NodeList	array<object>	The information about the nodes returned.
Node	object
SchedulerType	string	The scheduling type of the node. Valid values: NORMAL: The node is an auto triggered node. The scheduling system regularly runs the node. MANUAL: The node is a manually triggered node. The scheduling system does not regularly run the node. PAUSE: The node is a frozen node. The scheduling system regularly runs the node but sets the status of the node to failed when the scheduling system starts to run the node. SKIP: The node is a dry-run node. The scheduling system regularly runs the node but sets the status of the node to successful when the scheduling system starts to run the node.	NORMAL
RepeatInterval	integer	The interval at which the node is rerun after the node fails to run.	60
Repeatability	boolean	Indicates whether the node can be rerun.	true
FileType	string	The node type. Valid values: 6 (Shell), 10 (ODPS SQL), 11 (ODPS MR), 23 (Data Integration), 24 (ODPS Script), 99 (zero load), 221 (PyODPS 2), 225 (ODPS Spark), 227 (EMR Hive), 228 (EMR Spark), 229 (EMR Spark SQL), 230 (EMR MR), 239 (OSS object inspection), 257 (EMR Shell), 258 (EMR Spark Shell), 259 (EMR Presto), 260 (EMR Impala), 900 (real-time synchronization), 1089 (cross-tenant collaboration), 1091 (Hologres development), 1093 (Hologres SQL), 1100 (assignment), and 1221 (PyODPS 3)	ODPS_SQL
ProjectId	long	The workspace ID.	33671
ProgramType	string	The node type. This parameter is deprecated. For more information about node types, see valid values of the FileType parameter.	ODPS_SQL
Priority	integer	The priority of the node. Valid values: 1, 3, 5, 7, and 8. A greater value indicates a higher priority. Default value: 1.	1
OwnerId	string	The owner ID.	19337906836551
Connection	string	The name of the data source.	odps_first
ParamValues	string	The scheduling parameters of the node.	a=b
RelatedFlowId	long	The ID of the workflow to which the node belongs.	1235655464
DqcType	integer	Indicates whether the node is associated with a monitoring rule in Data Quality. Valid values: 0 and 1. The value 0 indicates that the node is associated with a monitoring rule in Data Quality. The value 1 indicates that the node is not associated with a monitoring rule in Data Quality.	1
BaselineId	long	The baseline ID.	1235667
Description	string	The description of the node.	test
NodeName	string	The name of the node.	liux_test_n****
ResGroupName	string	The name of the resource group.
DqcDescription	string	The table and partition filter expression in Data Quality that are associated with the node.	[{"projectName":"ztjy_dim","tableName":"dim_user_agent_manage_area_a","partition":"ds\u003d$[yyyy-mm-dd-1]"}]
CronExpress	string	The CRON expression.	00 00 00 * * ?
NodeId	long	The node ID.	125677

Examples

Sample success responses

JSONformat

{
  "HttpStatusCode": 200,
  "RequestId": "SDFSDFSDF-asdfDFSDF-SDFSDf-SDfSFD",
  "ErrorMessage": "The connection does not exist.",
  "ErrorCode": "Invalid.Tenant.ConnectionNotExists",
  "Success": true,
  "Data": [
    {
      "Output": "test_0709_1.630003556_out",
      "NodeList": [
        {
          "SchedulerType": "NORMAL",
          "RepeatInterval": 60,
          "Repeatability": true,
          "FileType": "ODPS_SQL",
          "ProjectId": 33671,
          "ProgramType": "ODPS_SQL",
          "Priority": 1,
          "OwnerId": "19337906836551",
          "Connection": "odps_first",
          "ParamValues": "a=b",
          "RelatedFlowId": 1235655464,
          "DqcType": 1,
          "BaselineId": 1235667,
          "Description": "test",
          "NodeName": "liux_test_n****",
          "ResGroupName": "",
          "DqcDescription": "[{\"projectName\":\"ztjy_dim\",\"tableName\":\"dim_user_agent_manage_area_a\",\"partition\":\"ds\\u003d$[yyyy-mm-dd-1]\"}]",
          "CronExpress": "00 00 00 * * ?",
          "NodeId": 125677
        }
      ]
    }
  ]
}

Error codes

For a list of error codes, visit the Service error codes.

Change history

Change time	Summary of changes	Operation

No change history