RDS SQL

Node Name

Yes

Name of a node. The name must contain 1 to 128 characters, including only letters, numbers, underscores (_), hyphens (-), slashes (/), less-than signs (<), and greater-than signs (>).

By default, the node name is the same as that of the selected script. If you want the node name to be different from the script name, disable this function by referring to Disabling Auto Node Name Change.

Data Connection

Yes

Name of the data connection.

Database

Yes

Name of the database. The database has been created. You are advised not to use the default database.

SQL or Script

Yes

You can select SQL statement or SQL script.

• SQL statement

  Click the text box under SQL statement and enter the SQL statement to be executed.

• SQL script

  Select a script to be executed. If no script is available, create and develop a script by referring to Creating a Script and Developing an SQL Script.

  NOTE:

  If you select the SQL statement mode, the DataArts Factory module cannot parse the parameters contained in the SQL statement.

Node Status Polling Interval (s)

Yes

How often the system check completeness of the node. The value ranges from 1 to 60 seconds.

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 be executed again.

Retry upon Failure

Yes

Whether to re-execute a node if it fails to be executed. Possible values:

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

  If retry is configured for a job node and the timeout duration is configured, the system allows you to retry a node when the node execution times out.

  If a node is not re-executed when it fails upon timeout, you can go to the Default Configuration page to modify this policy.

  Retry upon Timeout is displayed only when Retry upon Failure is set to Yes.

Policy for Handling Subsequent Nodes If the Current Node Fails

Yes

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

• Suspend execution plans of the subsequent nodes: stops running subsequent nodes. The job instance status is Failed.
• End the current job execution plan: stops running the current job. The job instance status is Failed.
• Go to the next node: ignores the execution failure of the current node. The job instance status is Failure ignored.
• Suspend the current job execution plan: If the current job instance is in abnormal state, the subsequent nodes of this node and the subsequent job instances that depend on the current job are in waiting state.

Enable Dry Run

No

If you select this option, the node will not be executed, and a success message will be returned.