Manually triggered node - DataWorks - Alibaba Cloud Documentation Center

If you have a node that does not need to run on a schedule but must be published to the production environment, you can create it as a manually triggered node. This topic describes how to create a manually triggered node and publish it to the production environment.

Usage notes

If a node does not need to be published to the production environment, you can create and execute it in a personal directory. This applies even if the node needs to access the DPI engine in the production environment.
manually triggered nodes can only be manually triggered and do not support automatic scheduling.
You can create only the following types of manually triggered nodes: Batch 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 navigation pane on the left, find the icon. Click > Create Node next to manually triggered nodes and select the type of node that you want to create. For more information about the supported node types, see the Usage notes section.
Enter a name for the manually triggered node and press Enter to open the code editor for the node.
After you write the code for the manually triggered node, click Run Configuration on the left side. As prompted, configure the Computing Resource and Resource Group to run the node. If script parameters are configured in the node, you must also assign values under Script Parameters.
Note
The Select Data Source option above the code enables metadata auto-completion.
Click Run at the top of the file to execute the current node and view the results.
After a manually triggered node runs, you can set its scheduling configurations and click Publish to publish the node to the production environment.
Follow the on-screen instructions to publish the manually triggered node.

Run a manually triggered node in the production environment

After the node is published, you can click Go To Operation Center to view the node in the Operation Center.
Note
Alternatively, you can go to the DataWorks Workspaces page. In the top navigation bar, switch to the destination region, find your workspace, and in the Actions column, click Quick Access > Operation Center to go to data administration. Then, in the navigation pane on the left, find manually triggered node O&M.
Run the manually triggered node.

Other operations

Clone a manually triggered node

You can use the clone feature to quickly create a new manually triggered node from an existing one. The cloned node includes the Scheduling Configuration, such as Scheduling Parameters and Scheduling Policies.

In the manually triggered node section on the left, right-click the node to clone and select Clone from the pop-up menu.
In the pop-up window, modify the Name and Path or keep the default values. Then, click Confirm to start cloning.
After the cloning is complete, the new manually triggered node appears in the manually triggered node section.

Version management

You can use the version management feature to revert a manually triggered node to a previous version. This feature also lets you view and compare versions, which helps you analyze differences and make adjustments.

In the manually triggered node section on the left, double-click the name of the desired manually triggered node to open its code editor.
On the right side of the code editor for the manually triggered node, click Versions. On the Versions page, you can view and manage Developer Records and Publish Records.
- View versions:
  1. On the Developer Records or Publish Records tab, locate the manually triggered node version you want to view.
  2. Click View in the Actions column to view the code content and Scheduling Configuration of the manually triggered node on the product page.
    Note
    You can view the Scheduling Configuration in either Code Editor or Visualization mode. You can switch between these modes in the upper-right corner of the Scheduling Configuration tab.
- Compare versions:
  On the Developer Records or Publish Records tab, you can compare different versions of a manually triggered node. This topic uses the Developer Records tab as an example.
  - Compare versions in the developer or production environment: On the Developer Records tab, select two versions of a manually triggered node and click the Compare Selected button to compare their code and scheduling configurations.
  - Compare versions between the developer environment and the production or build environment:
    1. On the Developer Records tab, find the manually triggered node.
    2. Click the Compare button in the Actions column. On the product page, select a version from Publish Records or Build Records to compare.
- Revert a version:
  You can revert a manually triggered node to a specific historical version in Developer Records. On the Developer Records tab, find the target version and click the Revert button in the Actions column to revert the node's code and Scheduling Configuration.