Updated on 2022-02-22 GMT+08:00

OBS Manager

Function

The OBS Manager node is used to move or copy files from an OBS bucket to a specified directory.

Parameters

Table 1 and Table 2 describe the parameters of the OBS Manager node.

Table 1 Parameters of OBS Manager nodes

Parameter

Mandatory

Description

Node Name

Yes

Name of the node. Must consist of 1 to 128 characters and contain only letters, digits, underscores (_), hyphens (-), slashes (/), less-than signs (<), and greater-than signs (>).

Operation Type

Yes

Operations that can be performed on the node.

  • Move File
  • Copy File

Source File

Yes

OBS file to be moved or copied from the OBS bucket.

Target Directory

Yes

Directory for storing OBS files to be moved or copied from the OBS bucket.

File Filter

No

Wildcard for file filtering. Only the files that meet the filtering condition can be moved or copied. If this parameter is not specified, all source files are moved or copied by default. For example, when you enter *.csv, files in this format will be moved or copied.

Table 2 Advanced parameters

Parameter

Mandatory

Description

Max. Node Execution Duration

Yes

Execution timeout interval for the node. If retry is configured and the execution is not complete within the timeout interval, the node will not be retried and is set to the failed state.

Retry upon Failure

Yes

Indicates whether to re-execute a node task if its execution fails. Possible values:

  • Yes: The node task will be re-executed, and the following parameters must be configured:
    • Maximum Retries
    • Retry Interval (seconds)
  • No: The node task will not be re-executed. This is the default setting.
NOTE:

If Timeout Interval is configured for the node, the node will not be executed again after the execution times out. Instead, the node is set to the failure state.

Failure Policy

Yes

Operation that will be performed if the node task fails to be executed. Possible values:

  • End the current job execution plan
  • Go to the next job
  • Suspend the current job execution plan
  • Suspend execution plans of the current and subsequent nodes