This topic describes how to create a workflow, create nodes in the workflow, and configure the dependencies. After you create a workflow, you can use the DataStudio service to further compute and analyze data in the workspace.
Prerequisites
Background information
Create a workflow
Create nodes and configure dependencies
- A zero load node is a control node that is used to maintain and control its descendant nodes in a workflow. A zero load node does not affect data.
- If other nodes depend on a zero load node and the zero load node is set to Failed by an administration expert, the pending descendant nodes cannot be triggered. During the O&M process, a zero load node can be disabled to prevent errors of ancestor nodes from being further expanded.
- Typically, the root node of the workspace is used as the ancestor node of a zero load
node in a workflow. The root node of a workspace is named in the
Workspace name_root
format. - DataWorks automatically creates an output name for a node, in the Workspace name. Node name format. If a workspace contains two nodes with the same name, modify the output name of one of the nodes.
When you design a workflow, we recommend that you create a zero load node as the root node of the workflow to control the entire workflow. To design a workflow, perform the following steps:
Configure the parent node of the zero load node
In a workflow, a zero load node is often used to control the entire workflow and serves as the ancestor node of all nodes in the workflow.
Generally, a zero load node depends on the root node of the workspace.
- Double-click the name of the zero load node to go to the node configuration tab.
- Click Properties in the right-side navigation pane.
- In the Dependencies section, click Use Root Node to configure the root node of the workspace as the parent node of the zero load node.
- Click the
icon in the toolbar.
Edit and run the ODPS SQL node
This section uses SQL code to query and save the number of singles with different education levels who loan to buy houses in the ODPS SQL node insert_data. The descendant nodes can continue to analyze and present the results.
Commit the workflow
- After you run and debug the ODPS SQL node insert_data, return to the configuration tab of the workflow.
- Click the
icon.
- In the Commit dialog box, select the nodes to be committed, enter your comments in the Change description field, and then select Ignore I/O Inconsistency Alerts.
- Click Commit.
What to do next
Now you have learned how to create and commit a workflow. You can proceed with the next tutorial. In the next tutorial, you will learn how to create a sync node to export data to different types of data stores. For more information, see Create a sync node.