Help Center/ DataArts Studio/ User Guide/ DataArts Factory/ Node Reference/ DIS Dump
Updated on 2024-07-11 GMT+08:00
View PDF
Share

DIS Dump

Functions

The DIS Dump node is used to configure data dump tasks in DIS.

Parameters

Table 1 and Table 2 describe the parameters of the DIS Dump node.

Table 1 Parameters of DIS Dump nodes

Parameter

Mandatory

Description

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 (>).

Stream Name

Yes

Select or enter the DIS stream to query. When entering the stream name, you can reference job parameters and use the EL expression. For details, see Expression Overview.

To create a DIS stream, you can use either of the following methods:
  • Click . On the Stream Management page of DLF, create a DIS stream.
  • Go to the DIS console to create a DIS stream.

Duplicate Name Policy

Yes

Select a duplicate name policy. If the name of a dump task already exists, you can adopt either of the following policies based on site requirements:

  • Ignore: Give up adding the dump task and exit DIS Dump. The status of DIS Dump is Succeeded.
  • Overwrite: Continue to add the dump task by overwriting the one with the same name.

Dump Destination

Yes
  1. Destination to which data is dumped. Possible values:
    • OBS: After the streaming data is stored to DIS, it is then periodically imported to OBS. After the real-time file data is stored to DIS, it is imported to OBS immediately.
  2. Click . In the dialog box that is displayed, set dump parameters. For details, see "Managing a Dump Task" in Data Ingestion Service User Guide.
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 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.

Task Groups

No

Select a task group. If you select a task group, you can control the maximum number of concurrent nodes in the task group in a fine-grained manner in scenarios where a job contains multiple nodes, a data patching task is ongoing, or a job is rerunning.
Parent topic: Node Reference