NodeEach type of node is used to perform a specific data operation. For example:A sync node is used to synchronize data from ApsaraDB for RDS to MaxCompute.An ODPS SQL node is used to convert data by executing SQL statements that are supported byMaxCompute.Each node has zero or more input tables or datasets and generates one or more output tablesor datasets.Nodes are classified into node tasks, flow tasks, and inner nodes.TypeDescriptionNode taskA node task is used to perform a data operation. You can configuredependencies between a node task and other node tasks or flow tasks toform a directed acyclic graph (DAG).Product Introduction ·Basic conceptsDataWorks8> Document Version:20200903
Flow taskA flow task contains a group of inner nodes that process a workflow. Werecommend that you create less than 10 flow tasks.Inner nodes in a flow task cannot be depended upon by other flow tasks ornode tasks. You can configure dependencies between a flow task andother flow tasks or node tasks to form a DAG.NoteIn DataWorks V2.0 and later, you can find the flow tasks thatare created in DataWorks V1.0 but cannot create flow tasks. Instead,you can create workflows to perform similar operations.Inner nodeAn inner node is a node within a flow task. Its features are basically thesame as those of a node task. You can configure dependencies betweeninner nodes in a flow task by performing drag-and-drop operations.However, you cannot configure a recurrence for inner nodes because theyfollow the recurrence configuration of the flow task.TypeDescriptionInstanceAn instance is a snapshot of a node at a specific time point. An instance is generated every timea node is run as scheduled by the scheduling system or manually triggered. An instance containsinformation such as the time point at which the node is run, the running status of the node, andoperational logs.Assume that Node 1 is configured to run at 02:00 every day. The scheduling systemautomatically generates an instance of Node 1 at 23:30 every day. At 02:00 the next day, if thescheduling system verifies that all the ancestor instances are run, the system automaticallyruns the instance of Node 1.NoteYou can query the instance information on the Cycle Instancepage of OperationCenter.CommitYou can commit nodes and workflows from the development environment to the schedulingsystem. The scheduling system runs the code in the committed nodes and workflows asconfigured.NoteThe scheduling system runs nodes and workflows only after you commit them.ScriptA script stores code for data analysis. The code in a script can be used only for data query andanalysis. It cannot be committed to the scheduling system for scheduling.Resource and functionResources and functions are concepts in MaxCompute. For more information, see ResourceandFunction.