Manually triggered nodes-DataWorks(DataWorks)-阿里云帮助中心

Usage notes

If a task does not need to be published to the production environment, you can create and run it in your personal directory.
Manually triggered nodes run only on-demand and do not support automatic scheduling.
You can create a manually triggered node only for the following node types: Offline synchronization, MaxCompute SQL, MaxCompute Script, PyODPS 2, MaxCompute MR, Hologres SQL, Python node, and Shell node.

Create and publish a manually triggered node

Go to the Workspaces page in the DataWorks console. In the top navigation bar, select a desired region. Find the desired workspace and choose Shortcuts > Data Studio in the Actions column.
In the left-side navigation pane, find the icon. To the right of Manually Triggered Task, click the > New Node. Select the type of manually triggered node to create. For more information about the supported node types, see Usage notes.
Enter a name for the node and press Enter to open the node editor.
After you write the code for the node, click Run Configuration in the left-side pane. As prompted, configure the Compute Resource and Resource Group to run the task. If script parameters are configured for the task, you must also assign values to the Script Parameters.

Note
The Select a data source option above the code editor provides metadata auto-completion as you write code.
Click Run at the top of the file to run the current task and view the results.
After the manually triggered node is run, you can configure its Publish and then click Publish.

Follow the on-screen instructions to publish the node.

Run a manually triggered node in production

After the node is published, click Go to operation and maintenance to view the node.

Note
You can also go to the DataWorks workspace list page. In the top navigation bar, select the target region. Find your workspace and click Shortcuts > Operation and Maintenance Center in the Operation column. In the left-side navigation pane of Operation Center, find Manually Triggered Task O&M.
Run the manually triggered node.

Other operations

Clone a manually triggered node

You can clone an existing manually triggered node to quickly create a new one. The cloned content includes the node's Scheduling Settings, such as Scheduling Parameters and Scheduling Policy.

In the Manually Triggered Task section in the left-side navigation pane, right-click the manually triggered node to clone and select Cloning.
In the dialog box that appears, change the Name and Path or keep the default settings. Then, click Confirm to start cloning.
After the node is cloned, the new node appears in the Manually Triggered Task section.

Version management

Version management lets you revert a manually triggered node to a previous version. You can also view and compare versions to identify changes.

In the Manually Triggered Task section on the left, double-click the desired manually triggered node to open the node editor.
On the right side of the node editor, click Version. On the Version panel, you can view and manage information on the Developer Record and Publish Record tabs.
- View a version
  1. On the Developer Record or Publish Record tab, find the version of the manually triggered node that you want to view.
  2. Click View in the Operation column to go to the details page. On this page, you can view the code and Scheduling Settings of the node.
    
    Note
    You can view the Scheduling Settings in Code Editor or Visualization mode. You can switch between the modes in the upper-right corner of the Scheduling Settings tab.
- Compare versions
  
  You can compare different versions of manually triggered nodes on the Developer Record or Publish Record tab. This topic uses the Developer Record tab as an example to demonstrate this operation.
  - Compare versions within the development or publishing environment: On the Developer Record tab, select two versions and click Select Comparison to compare the code and scheduling configuration of the two versions.
  - Development vs. release or build environments:
    1. On the Developer Record tab, find a version of the manually triggered node.
    2. Click Compare in the Operation column. On the details page, select a version from the Publish Record or Build Records tab to compare.
- Restore to a version
  
  You can revert a node to a previous version only from the Developer Record tab. On the Developer Record tab, find the version to which you want to revert the node and click Restore in the Operation column. This reverts the node's code and Scheduling Settings to the selected version.