DataWorks node version management-DataWorks(DataWorks)-阿里云帮助中心

Each successful commit of a node or workflow creates a new version. You can use the Versions panel to review the commit history, check change types, compare versions, and roll back a node or workflow to a specific version. This topic uses a node to explain the version management features. The process for workflows is similar.

Go to the node editing page

Log on to the DataWorks console. In the target region, click Data Development and O&M > Data Development in the left-side navigation pane. Select a workspace from the drop-down list and click Go to Data Development.
Go to the node editing page.

In the directory tree on the left side of the Data Studio page, find the target node and double-click the node name to open its editing page.

View and roll back node versions

On the node editing page, click Version in the right-side navigation pane to view the node's version history. The following table describes the main parameters.

Parameter	Description
Change Type	The change type is New for the first commit and Modify for subsequent commits.
Status	Submitted: The node has been committed to the development environment but has not been included in a deployment package or deployed to the production environment. You can go to the deployment page to deploy the node. For more information, see Deploy tasks. Intermediate Version: The node has been committed to the development environment and included in a deployment package, but has not been deployed to the production environment. The node is pending deployment. You can go to the deployment page to deploy the node. For more information, see Deploy tasks. Published: The node has been committed to the development environment and deployed to the production environment.
Operation	View: View the task code and scheduling configuration for the selected version. Compare: Compare a version with the currently saved version, or compare any two versions. Note You can compare a maximum of two versions at a time. Roll Back: Roll back the node to the desired version. Note Rolling back to a version overwrites the current content of the node. After you roll back, you must commit the node again for the rollback to take effect.

Compare versions

You can compare node versions from the following locations:

On the DataStudio page, double-click a node name to open its editing page. Compare node versions in the Version panel on the right.
On the deployment page, compare the version of a task to be deployed with the version in the production environment to review the changes.

The following table describes the parameters displayed in the version comparison.

Parameter	Description
appId	The ID of the node's DataWorks workspace. You can go to the workspace configuration page to view the ID.
createUser	The ID of the user who created the node.
createTime	The time when the node was created.
lastModifyUser	The ID of the user who last modified the node.
lastModifyTime	The time when the node was last modified.
owner	The ID of the node owner. You can find this on the Scheduling > General page. For more information, see Configure basic properties.
startRightNow	Specifies how periodic instances are generated. Valid values: 0: Instances are generated Next Day. 1: Instances are generated Immediately After Deployment. For more information, see Instance generation modes.
taskRerunTime	The number of times the node is automatically rerun.
taskRerunInterval	The automatic rerun interval. Unit: milliseconds.
reRunAble	Indicates whether the node can be rerun. Valid values: 0: The node can be rerun Do not re-run after successful operation, and re-run after failure.. 1: The node can be rerun regardless of its previous run status. 2: The node Disallow Regardless of Running Status, regardless of its previous run status.
startEffectDate	The date on which scheduling becomes effective.
endEffectDate	The date on which scheduling is no longer effective.
cycleType	The scheduling cycle type. Valid values: 0: Daily, weekly, monthly, or yearly scheduling. 1, 2, and 3: Minute-based or hour-based scheduling.
cronExpress	The cron expression that defines the schedule.
extConfig	Additional configurations in JSON format. Key fields include: ignoreBranchConditionSkip: Specifies whether to inherit the dry-run property from the previous cycle. For more information, see Inherit the dry-run property from an ancestor node. true: Inherit the dry-run property. false: Do not inherit the dry-run property. alisaTaskKillTimeout: The timeout period. Unit: hours.
resgroupId	The ID of the selected resource group for scheduling. For more information, see Configure resource properties.
isAutoParse	Indicates whether automatic parsing is enabled. Valid values: 1: Automatic parsing is enabled. 0: Automatic parsing is disabled. For more information, see Configure same-cycle scheduling dependencies.
input	The input and output configurations of the node. The fields include: str: The input or output value. refTableName: The output table. parseType: The method used to add inputs and outputs. Valid values: 0: Automatic parsing. 1: Manual addition. 2: System generation. The dependency is automatically generated based on data lineage. For more information, see Overview of scheduling dependency configuration.
inputList
output
outputList
dependentTypeList	The node's cross-cycle dependency type. Valid values: 0: No option is selected. 1: One or more specified nodes. 2: Level-1 descendant nodes. 3: The current node. For more information, see Configure cross-cycle dependencies.
dependentDataNode	A list of custom node IDs for cross-cycle dependencies. This parameter takes effect only when dependentTypeList is set to 1.
inputContextList	The node context configurations. For more information, see Configure node context.
outputContextList
isStop	Indicates whether to suspend scheduling for the node. Valid values: 0: Normal or dry-run scheduling 1: Suspended scheduling
tags	Reserved for future use.
tagList
fileId
dependentType

For more information about time properties, see Configure time properties.