This topic describes how to deploy nodes in a workspace in standard mode and how to use the cross-workspace cloning feature to clone and deploy nodes in a workspace in basic mode.
Background information
DataWorks workspaces in standard mode provide both the development environment and the production environment within a single workspace. We recommend that you use workspaces in standard mode to develop and produce data. For more information, see Basic mode and standard mode.
In a workspace in standard mode, committed nodes are automatically added to the Create Deploy Task page. This page displays created, updated, and deleted nodes, resources, and functions.

To make the nodes, resources, and functions that you create, update, or delete on the DataStudio page take effect in the production environment, you must deploy them to the production environment on the Create Deploy Task page. On the Create Deploy Task page, you can add one or more nodes to the list of nodes to be deployed and deploy the nodes at a time.
On the Create Deploy Task page, you can modify the number of items that can be displayed on each page.
Parameter | Description |
---|---|
appId | The ID of the DataWorks workspace to which the node belongs. You can go to the Workspace Management page to view the ID. For more information, see Configure a workspace. |
createUser | The ID of the user that created the node. |
createTime | The time when the node was created. |
lastModifyUser | The ID of the user that last modified the node. |
lastModifyTime | The time when the node was last modified. |
owner | The ID of the owner of the node. You can view the owner ID in the General section of the panel. For more information, see Configure basic properties. |
startRightNow | The mode in which auto triggered node instances are generated for the node. Valid
values:
|
taskRerunTime | The number of times for which the node is rerun. |
taskRerunInterval | The interval between two consecutive automatic reruns. Unit: milliseconds. |
reRunAble | Indicates whether the node can be rerun. Valid values:
|
startEffectDate | The start date and time of the period during which scheduling takes effect. |
endEffectDate | The end date and time of the period during which scheduling takes effect. |
cycleType | The scheduling type of the node. Valid values:
|
cronExpress | The CRON expression used for configuring periodic scheduling. |
extConfig | The additional configurations of the node. The value must be in the JSON format and
contains the settings of the following fields:
|
resgroupId | The ID of the resource group for scheduling used to run the node. For more information, see Configure the resource group. |
isAutoParse | Specifies whether to enable the automatic parsing feature for the node. Valid values:
|
input | The input and output configurations of the node. The parameter values contain the
settings of the following fields:
|
inputList | |
output | |
outputList | |
dependentTypeList | The previous-cycle scheduling dependencies of the node. Valid values:
|
dependentDataNode | The IDs of the one or more nodes that are specified as the previous-cycle scheduling dependencies of the node. This parameter is valid only if the dependentTypeList parameter is set to 1. |
inputContextList | The context-based input and output parameters of the node. For more information, see Configure context-based parameters. |
outputContextList | |
tags | The reserved parameters. |
tagList | |
fileId | |
isStop | |
dependentType |
- Nodes for which the Instance Generation Mode parameter is set to Next Day: If you update and deploy an auto triggered node before 23:30, instances are generated for the updated node the next day.
- Nodes for which the Instance Generation Mode parameter is set to Immediately After Deployment: If you create and deploy a node, instances whose scheduled time is 10 minutes later than the time when the node is deployed are generated as expected. If you update and deploy a node, instances whose scheduled time is 10 minutes later than the time when the node is deployed are generated again based on the latest scheduling configuration. These instances replace those that are generated before the update. For more information, see Configure immediate instance generation for a node.
- If you create or update a node and deploy the node after 23:30, instances are generated for the new or updated node on the third day.
- If you deploy a node after 23:30 and the Instance Generation Mode parameter is set to Immediately After Deployment, instances are not immediately generated for the node.
Deploy nodes in a workspace in standard mode
Each DataWorks workspace in standard mode is associated with two MaxCompute projects, one as the development environment and the other as the production environment. You can directly commit and deploy nodes from the development environment to the production environment.
Deploy nodes in a workspace in basic mode
If you want to isolate the development environment from the production environment when you use workspaces in basic mode, create two workspaces, one for development and the other for production. You can clone nodes from the development workspace to the production workspace.
- Permission requirement: Only workspace administrators and RAM users who are assigned the administration expert role can clone nodes. The administration expert role has permissions to create clone tasks and deploy cloned nodes.
- Supported workspace type: You can clone nodes only from workspaces in basic mode to other workspaces.
- Prerequisites: The source workspace in basic mode and the destination workspace in standard mode are created.