DLI SQL
Functions
The DLI SQL node is used to transfer SQL statements to DLI SQL for data source analysis and exploration.
Working Principles
This node enables you to execute DLI statements during periodical or real-time job scheduling. You can use parameter variables to perform incremental import and process partitions for your data warehouses.
Parameters
Table 1, Table 2, and Table 3 describe the parameters of the DLI SQLnode node.
Parameter |
Mandatory |
Description |
---|---|---|
SQL Statement or Script |
Yes |
You can select SQL statement or SQL script.
|
DLI Data Directory |
No |
Select the DLI data directory.
|
Database Name |
Yes |
If you select SQL script: Database that is configured in the SQL script. The value can be changed. If you select SQL Statement:
|
DLI Environmental Variable |
No |
|
Queue Name |
Yes |
Name of the DLI queue configured in the SQL script. The value can be changed.
You can create a resource queue using either of the following methods:
NOTE:
|
Script Parameter |
No |
If the associated SQL script uses a parameter, the parameter name is displayed. Set the parameter value in the text box next to the parameter name. The parameter value can be an EL expression. If the parameters of the associated SQL script are changed, click to refresh the parameters. |
Node Name |
Yes |
Name of the SQL script. The value can be changed. The rules are as follows: 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. |
Record Dirty Data |
Yes |
Click to specify whether to record dirty data.
|
Parameter |
Mandatory |
Description |
---|---|---|
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:
|
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. |
Parameter |
Description |
---|---|
Input |
|
Add |
Click Add. In the Type drop-down list, select the type to be created. The value can be DWS, OBS, CSS, HIVE, DLI, or CUSTOM. |
OK |
Click OK to save the parameter settings. |
Cancel |
Click Cancel to cancel the parameter settings. |
Modify |
Click to modify the parameter settings. After the modification, save the settings. |
Delete |
Click to delete the parameter settings. |
View Details |
Click to view details about the table created based on the input lineage. |
Output |
|
Add |
Click Add. In the Type drop-down list, select the type to be created. The value can be DWS, OBS, CSS, HIVE, DLI, or CUSTOM. |
OK |
Click OK to save the parameter settings. |
Cancel |
Click Cancel to cancel the parameter settings. |
Modify |
Click to modify the parameter settings. After the modification, save the settings. |
Delete |
Click to delete the parameter settings. |
View Details |
Click to view details about the table created based on the output lineage. |
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