MRS Hive SQL

Updated on 2022-02-22 GMT+08:00

View PDF

The MRS Hive SQL node is used to execute a predefined Hive SQL script on DLF.

Table 1 and Table 2 describe the parameters of the MRS Hive SQL node.

**Table 1** Parameters of MRS Hive SQL nodes
Parameter	Mandatory	Description
SQL Script	Yes	Path to a script to be executed. If the script is not created, create and develop the 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 a built-in function and EL expression. For details about built-in functions and EL expressions, see Expression Overview. 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 SparkSQL jobs, see Running a HiveSql Job > Table 2 Program Parameter parameters in the MapReduce User Guide.
Node Name	Yes	Name of the SQL script. The value can be changed. The rules are as follows: Name of the node. Must consist of 1 to 128 characters and contain only letters, digits, underscores (_), hyphens (-), slashes (/), less-than signs (<), and greater-than signs (>).

**Table 2** Advanced parameters
Parameter	Mandatory	Description
Node Status Polling Interval (s)	Yes	Specifies how often the system check completeness of the node task. 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 not be retried and is set to the failed state.
Retry upon Failure	Yes	Indicates whether to re-execute a node task if its execution fails. Possible values: Yes: The node task will be re-executed, and the following parameters must be configured: Maximum Retries Retry Interval (seconds) No: The node task will not be re-executed. This is the default setting. NOTE: If Timeout Interval 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	Operation that will be performed if the node task fails to be executed. Possible values: End the current job execution plan Go to the next job Suspend the current job execution plan Suspend execution plans of the current and subsequent nodes

Parent topic: Nodes

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.