All Products
Document Center

Virtual node task

Last Updated: Apr 10, 2018

A virtual node is a control node that does not generate any data. Generally, it is used as the root node of overall planning nodes in the workflow.


The final output table of a workflow contains multiple branch input tables. Virtual nodes are usually used if these input tables are not dependent.


An output table is generated after the source tables imported by three data synchronization tasks are processed by the ODPS_SQL task. The three data synchronization tasks are not dependent, but the ODPS_SQL task is dependent on the three data synchronization tasks. The workflow is shown as follows.


A virtual node is used as the root node where the workflow starts. The three data synchronization tasks depend on the virtual node and the ODPS_SQL processing task is dependent on the three data synchronization tasks.

Create a virtual node task

  1. On the Data Development page, click New and select Create Task.


  2. Complete the configurations in the Create Task dialog box.

    Select Workflow Task as the task type and Periodic Scheduling as the scheduling type.


  3. Click Create to redirect to the workflow designer page.

  4. Double-click Virtual in Nodes list.


  5. After entering the node name, click Create to obtain the following virtual nodes.


Run the virtual node task

The workflow dataworks1 was created in the previous section, so only one virtual node task is in the workflow.

  1. Click Test Run.


  2. Click OK in the Running Reminder for Periodic Tasks dialog box.

  3. Click Run in the Test Run dialog box.

Check the task running status

  1. Click Go to O&M Center in the Workflow Task Test Run dialog box.


  2. Double-click the workflow name to enter the workflow.

    Then, you can see the running status of the nodes in the workflow.

  3. Click the virtual node, and select Operation Log.

    Task log prompt: No data.


    Reason: The virtual node task is set as running successfully when the virtual node runs but does not run actually, so the task does not generate any log information.