Updated on 2026-11-12 GMT+08:00

MRS Hive SQL

Functions

The MRS Hive SQL node is used to execute a predefined Hive SQL script in DataArts Factory. This node can transfer SQL statements to Hive, including DML and DDL SQL statements.

Hive is a data warehouse infrastructure built on top of Hadoop. It can be used to extract, transform, and load data. Hive is a mechanism that can store, query, and analyze mass data stored on Hadoop. Hive defines a simple SQL-like query language, which is known as Hive SQL langage (HQL). It allows a user familiar with SQL to query data.

For details about how to use the MRS Hive SQL node, see Developing a Hive SQL Job.

MRS Hive SQL nodes do not support Hive transaction tables.

Terms

Program parameters: command line parameters transferred to the Hive CLI or Tez/MapReduce engine. Generally, the parameters start with --hiveconf and overwrite the default configuration.

Parameters

Table 1, Table 2, and Table 3 describe the parameters of the MRS Hive SQLnode node.

Table 1 Parameters

Parameter

Mandatory

Description

Node Name

Yes

Name of the job node

The node name must contain 1 to 128 characters, including only letters, digits, and the following special characters: _-/.<>

If the MRS job name is not set and the direct connection mode (API mode) is selected, the node name can contain only letters, digits, hyphens (-), and underscores (_).

NOTE:

The node name cannot contain other characters or more characters than allowed. If the node name does not meet requirements, the MRS job will fail to be submitted.

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.

MRS Job Name

No

MRS job name.

MRS job name. It can contain a maximum of 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.

The system can automatically enter an MRS job name in Job name_Node name format.

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.

NOTE:

A script can transfer a maximum of 50 parameters to a job node. A parameter name can contain no more than 64 characters, and a parameter value can contain no more than 256 characters.

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. You can click Edit to edit the parameter expression.

If the parameters of the associated SQL script are changed, click to refresh the parameters.

Data Connection

Yes

Data connection that is configured in the SQL script. The value can be changed.

MRS Hive data connections include direct and indirect connections. If the direct connection mode is selected for the SQL script, a direct connection is displayed.

Database

Yes

Database that is configured in the SQL script. The value can be changed.

If you select an MRS API connection (direct connection), you cannot select a database, and this parameter is dimmed.

MRS Resource Queue

No

Select a created MRS resource queue.

If you have configured Resource Queue Mapping, the name of the PatchData queue mapped to the selected MRS resource queue is displayed. Currently, this function is supported only in simple mode and not in enterprise mode.

NOTE:

Select a queue you configured in the queue permissions of DataArts Security. If you set multiple resource queues for this node, the resource queue you select here has the highest priority.

Test Queue

No

The default test queue name is displayed if you have configured a test queue in Resource Queue Mapping. If you have not configured a test queue, you can manually select one. The test queue must be one that does not require approval.

Currently, this function is supported only in simple mode and not in enterprise mode.

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.

For Hive proxy connections, only resource queue parameters can be configured.

Example 1: Set the parameter name to --hiveconf and the parameter value to mapreduce.job.queuename=default.

Example 2: Adjust MapReduce resources (most commonly used).

Hive generally runs on the MapReduce engine. If the job is running slowly, you can adjust resources by setting parameters.

Example parameters (for the MapReduce engine):

--hiveconf mapreduce.map.memory.mb=4096

--hiveconf mapreduce.reduce.memory.mb=8192

--hiveconf mapreduce.map.cpu.vcores=2

--hiveconf mapreduce.reduce.cpu.vcores=4

Descriptions:

mapreduce.map.memory.mb=4096: 4 GB of memory for Map tasks

mapreduce.reduce.memory.mb=8192: 8 GB of memory for Reduce tasks

mapreduce.map.cpu.vcores=2: number of CPUs for Map tasks

mapreduce.reduce.cpu.vcores=4: number of CPUs for Reduce tasks

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 Running a HiveSql Job > Table 2 Program Parameter parameters in the MapReduce Service User Guide.

Table 2 Advanced parameters

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:

  • 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.

Table 3 Lineage

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.