MRS Hive SQL
Function
The MRS Hive SQL node is used to execute a predefined Hive SQL script on DLF.
Parameters
Table 1, Table 2, and Table 3 describe the parameters of the MRS Hive SQL node.
Parameter |
Mandatory |
Description |
---|---|---|
SQL Script |
Yes |
Path of 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. |
Data Connection |
Yes |
Data connection that is configured in the SQL script. The value can be changed. |
Database |
Yes |
Database that is configured in the SQL script. The value can be changed. |
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. |
Program Parameter |
No |
Used to configure optimization parameters such as threads, memory, and vCPUs for the job to optimize resource usage and improve job execution performance.
NOTE:
This parameter is mandatory if the cluster version is MRS 1.8.7 or later than MRS 2.0.1. For details about the program parameters of MRS Hive SQL jobs, see Managing an Existing Cluster > Job Management > Running a Hive SQL Job in the MapReduce Service (MRS) User Guide. |
Node Name |
Yes |
Name of the SQL script. The value can be changed. The rules are as follows: Node name. It contains 1 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
NOTE:
The node name cannot contain more than 64 characters. If the node name does not meet requirements, the MRS job will fail to be submitted. |
Parameter |
Mandatory |
Description |
---|---|---|
Node Status Polling Interval (s) |
Yes |
How often the system checks completeness of the node task. The value ranges from 1 to 60 seconds. |
Max. Node Execution Duration |
Yes |
Maximum duration of executing a node. When Retry upon Failure is set to Yes for a node, the node can be re-executed for numerous times upon an execution failure within the maximum duration. |
Retry upon Failure |
Yes |
Whether to re-execute a node after the node fails to be executed.
NOTE:
If Max. Node Execution Duration 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 |
Policies to be performed after the node fails to be executed:
|
Dry run |
No |
If you select this option, the node will not be executed, and a success message will be returned. |
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