DIS Client
Functions
The DIS Client node is used to send messages to a DIS stream.
You can learn more about how to use the DIS Client node in Scheduling Jobs Across Workspaces.
Parameters
Table 1 describes the parameters of the DIS Client node.
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 (>). |
Using DIS Connection |
No |
If DIS streams are used, messages can be sent to the DIS streams of another account. Otherwise, messages can be sent only to streams in all regions of the current account. |
DIS Connection |
No |
This parameter is mandatory only when Using DIS Connection is set to Yes. Before setting this parameter, ensure that you have created a DIS connection in the Management Center by referring to Creating Data Connections. This parameter is not required when Using DIS Connection is set to No. |
Region |
No |
Region that the target DIS stream belongs to. The DIS Client node is used to send messages to the target DIS stream. |
Stream Name |
Yes |
DIS stream to which messages will be sent. You can enter a stream address or select a stream. |
Sent Data |
Yes |
Text sent to the DIS stream. You can directly enter text or click to use the EL expression. |
Related Job |
No |
Select batch or real-time processing jobs. You can select a maximum of 10 jobs. This parameter allows you to switch to the monitoring page of the selected jobs when they start running. After selecting a job, click Monitor. On the Monitory Job page, select the DIS Client node and click View Related Job on the lower part of the page. In the View Related Job dialog box, click View in the Operation column of a job to view the details about the job. |
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:
|
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:
|
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. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot