DataWorks:UpdateFile

The path to the folder where the file is located.

The DataWorks workspace ID. To obtain the ID, log on to the DataWorks console and navigate to the workspace management page.

The file name. You can modify the file name by setting a new value for FileName. For example, you can call the ListFiles operation to query the file ID in the target directory, and then call the UpdateFile operation with the file ID specified in the FileId parameter and a new value specified in the FileName parameter to modify the file name.

The file description.

The file code content. Different code types (fileType) have different code formats. In Operation Center, you can right-click a task of the corresponding type and select View Code to view the specific code format.

The number of automatic reruns after the file execution fails.

The interval at which the node is automatically rerun after a failure. Unit: milliseconds. Maximum value: 1800000 milliseconds (30 minutes).

This parameter corresponds to the Rerun interval parameter in Properties > Schedule > Auto Rerun upon Failure for data development nodes in the DataWorks console. In the console, the unit of the rerun interval is minutes. Convert the time unit when you call this operation.

The rerun policy. Valid values:

• ALL_ALLOWED: Reruns are allowed regardless of whether the task succeeds or fails.
• FAILURE_ALLOWED: Reruns are allowed only when the task fails.
• ALL_DENIED: Reruns are not allowed regardless of whether the task succeeds or fails.

This parameter corresponds to the Support for Rerun setting in Scheduling > Scheduling Policies for Data Studio tasks in the DataWorks console.

Valid values:

• ALL_ALLOWD
• FAILURE_ALLOWED
• ALL_DENIED
• ALL_ALLOWED

Specifies whether to skip execution. Valid values:

• true
• false

This parameter corresponds to the Skip Execution option in Properties > Schedule > Recurrence for data development nodes in the DataWorks console.

The scheduling parameters of the node.

This parameter corresponds to the Scheduling Parameter setting in Properties for data development nodes in the DataWorks console. For more information, see Scheduling parameters.

The timestamp (in milliseconds) when automatic scheduling starts.

This parameter corresponds to the start time of Effective Period in Scheduling > Scheduling Time for Data Studio tasks in the DataWorks console.

The timestamp (in milliseconds) when automatic scheduling stops.

This parameter corresponds to the end time of Effective Period in Scheduling > Scheduling Time for Data Studio tasks in the DataWorks console.

The cron expression for scheduled execution. This parameter corresponds to the Cron Expression setting in Scheduling > Scheduling Time for Data Studio tasks in the DataWorks console. After you configure Scheduling Cycle and Scheduled Time, DataWorks automatically generates a cron expression.

Examples:

• Scheduled at 05:30 every day: 00 30 05 * * ?
• Scheduled at the 15th minute of every hour: 00 15 * * * ?
• Scheduled every 10 minutes: 00 00/10 * * * ?
• Scheduled every 10 minutes between 08:00 and 23:00 every day: 00 00-59/10 8-23 * * * ?
• Scheduled at 00:20 on the 1st day of every month: 00 20 00 1 * ?
• Scheduled every 3 months starting from 00:10 on January 1: 00 10 00 1 1-12/3 ?
• Scheduled at 00:05 on every Tuesday and Friday: 00 05 00 * * 2,5

Due to the rules of the DataWorks scheduling system, cron expressions have the following restrictions:

• The minimum scheduling interval is 5 minutes.
• The earliest scheduling time each day is 00:05.

The type of scheduling cycle. Valid values: NOT_DAY (minute, hour) and DAY (day, week, month).

This parameter corresponds to the Scheduling Cycle setting in Scheduling > Scheduling Time for Data Studio tasks in the DataWorks console.

The dependency mode on the previous cycle. Valid values:

• SELF: Depends on the current node.
• CHILD: Depends on the child nodes.
• USER_DEFINE: Depends on other nodes.
• NONE: No dependencies. Does not depend on the previous cycle.

The IDs of the nodes on which the current node depends. This parameter takes effect only when the DependentType parameter is set to USER_DEFINE. Separate multiple node IDs with commas (,).

This parameter corresponds to the Other Nodes option in Properties > Dependencies > Cross-cycle Dependency (Original Previous-cycle Dependency) for data development nodes in the DataWorks console.

The output names of the ancestor nodes on which the current node depends. Separate multiple output names with commas (,).

This parameter corresponds to the Output Name of Ancestor Node setting in Properties > Dependencies for data development nodes in the DataWorks console.

The DataWorks workspace name. To obtain the workspace name, log on to the DataWorks console and navigate to the workspace configuration page.

You must specify either this parameter or ProjectId to identify the target DataWorks workspace for this API call.

The file ID. You can call the ListFiles operation to obtain the file ID.

The outputs of the node.

This parameter corresponds to the Output Name setting in Properties > Dependencies for data development nodes in the DataWorks console.

The resource group for the task published from the file. You can call the ListResourceGroups operation to query the available resource groups in the workspace.

The name of the data source that is used to run the node. You can call the ListDataSources operation to query the available data sources.

The file owner ID.

Specifies whether to enable automatic parsing for the file. Valid values:

• true
• false

This parameter corresponds to the Analyze Code setting in Properties > Dependencies for data development nodes in the DataWorks console.

The scheduling type. Valid values:

• NORMAL: Normal scheduled task.
• MANUAL: Manually triggered node. Not scheduled for daily execution. Corresponds to nodes in manually triggered workflows.
• PAUSE: Paused task.
• SKIP: Dry-run task. Scheduled for daily execution but is directly marked as successful when scheduling starts.

The advanced settings for the task.

This parameter corresponds to the Advanced Settings in the right-side navigation pane on the editing page for EMR Spark Streaming and EMR Streaming SQL tasks in Data Studio in the DataWorks console.

Currently, only EMR Spark Streaming and EMR Streaming SQL tasks support this parameter, and the parameter must be in JSON format.

Specifies whether to start the task immediately after it is published. Valid values:

• true: Start the task immediately after it is published.
• false: Do not start the task immediately after it is published.

This parameter corresponds to the Start Method setting in Configuration > Scheduling Policies in the right-side navigation pane on the editing page for EMR Spark Streaming and EMR Streaming SQL tasks in Data Studio in the DataWorks console.

The input context parameters of the node. The value must be in the JSON format. For more information about the parameter structure, see the InputContextParameterList parameter in the response parameters of the GetFile operation.

This parameter corresponds to the Input Parameters setting in Properties > Input and Output Parameters for data development nodes in the DataWorks console.

The output context parameters of the node. The value must be in the JSON format. For more information about the parameter structure, see the OutputContextParameterList parameter in the response parameters of the GetFile operation.

This parameter corresponds to the Output Parameters setting in Properties > Input and Output Parameters for data development nodes in the DataWorks console.

This parameter corresponds to the Skip The Dry-Run Property Of The Ancestor Node option in Properties > Dependencies > Cross-cycle Dependency (Original Previous-cycle Dependency) when Instances of Current Node or Level-1 Child Node is selected for data development nodes in the DataWorks console.

Specifies whether to apply the scheduling configuration immediately after the file is published.

The timeout settings for scheduling configuration.

The custom image ID.