Creating a Hive Role

Updated on 2022-12-14 GMT+08:00

View PDF

Scenario

This section describes how to create and configure a Hive role on Manager as the system administrator. The Hive role can be granted the permissions of the Hive administrator and the permissions to operate Hive table data.

Creating a database with Hive requires users to join in the hive group, without granting a role. Users have all permissions on the databases or tables created by themselves in Hive or HDFS. They can create tables, select, delete, insert, or update data, and grant permissions to other users to allow them to access the tables and corresponding HDFS directories and files. The created databases or tables are saved in the /user/hive/warehouse directory of the HDFS by default.

NOTE:

A Hive role can be created only in security mode.
If the current component uses Ranger for permission control, you need to configure permission management policies based on Ranger. For details, see Adding a Ranger Access Permission Policy for Hive for MRS 3.x or later that supports Ranger.

Prerequisites

The system administrator has understood the service requirements.
Log in to FusionInsight Manager.
The Hive client has been installed.

Procedure

For versions earlier than MRS 3.x, perform the following operations to create a Hive role:

Log in to MRS Manager.
Choose System > Permission > Manage Role.
Click Create Role, and set Role Name and Description.

Set permissions. For details, see Table 1.

Hive Admin Privilege: Hive administrator permissions. If you want to use this permission, run the set role admin command to set the permission before running SQL statements.
Hive Read Write Privileges: Hive data table management permission, which is the operation permission to set and manage the data of created tables. Select the permissions of a database as required. To specify permissions on tables, click the database name and select the permissions of the tables.

NOTE:

Hive role management supports the administrator permission, and the permissions of accessing tables and views, without granting the database permission.
The permissions of the Hive administrator do not include the permission to manage HDFS.
If there are too many tables in the database or too many files in tables, the permission granting may last a while. For example, if a table contains 10,000 files, the permission granting lasts about 2 minutes.

**Table 1** Setting a role
Scenario	Role Authorization
Setting the Hive administrator permission	In the Permission table, click Hive and select Hive Admin Privilege. NOTE: After being bound to the Hive administrator role, perform the following operations during each maintenance operation: Log in to the node where the client is installed. Run the following command to configure environment variables: For example, if the Hive client installation directory is /opt/hiveclient, run source /opt/hiveclient/bigdata_env. Run the following command to authenticate the user: kinit Hive service user Run the following command to log in to the client tool: beeline Run the following command to update the administrator permissions: set role admin;
Setting the permission to query a table of another user in the default database	In the Permission table, choose Hive > Hive Read Write Privileges. In the Permission column of the specified table, select SELECT.
Setting the permission to query a table of another user in the default database	In the Permission table, choose Hive > Hive Read Write Privileges. In the Permission column of the specified table, select Insert.
Setting the permission to import data to a table of another user in the default database	In the Permission table, choose Hive > Hive Read Write Privileges. In the Permission column of the specified table, select Delete and Insert.
Setting the permission to submit HQL commands to Yarn for execution	The HQL commands used by some services are converted into MapReduce tasks and submitted to Yarn for execution. You need to set the Yarn permissions. For example, the HQL statements to be run use statements, such as insert, count, distinct, group by, order by, sort by, or join. In the Permission table, choose Yarn > Scheduler Queue > root. In the Permission column of the default queue, select Submit.

Click OK, and return to the Role page.
Choose System > Manage User > Create User.
Enter the username, set User Type to Human-machine, set the user password, add a user group bound with the Hive administrator role, bind the new Hive role to the user group, and click OK.
After the user is created, you can run the SQL statement using the user.

For MRS 3.x or later, perform the following operations to create a Hive role:

Log in to FusionInsight Manager. For details, seeAccessing FusionInsight Manager (MRS 3.x or Later)
Choose System > Permission > Role.
Click Create Role, and set Role Name and Description.

Set Configure Resource Permission. For details, see Table 2.

Grant the read and execution permissions for the HDFS directory.
- Click Name of the desired cluster and select HDFS for Service Name. On the displayed page, click File System, choose hdfs://hacluster/ > user, locate the row where hive is located, and select Read and Execute in the Permission column.
- Click Name of the desired cluster and select HDFS for Service Name. On the displayed page, click File System, choose hdfs://hacluster/ > user > hive, locate the row where warehouse is located, and select Read and Execute in the Permission column.
- Click Name of the desired cluster and select HDFS for Service Name. On the displayed page, click File System, choose hdfs://hacluster/ > tmp, locate the row where hive-scratch is located, and select Read and Execute in the Permission column.
Hive Admin Privilege: Hive administrator permission.
Hive Read Write Privileges: Hive data table management permission, which is the operation permission to set and manage the data of created tables.

NOTE:

In MRS 3.1.0, Hive role management supports the administrator permission, and the permissions of accessing tables and views, without granting the database permission.
The permissions of the Hive administrator do not include the permission to manage HDFS.
If there are too many tables in the database or too many files in tables, the permission granting may last a while. For example, if a table contains 10,000 files, the permission granting lasts about 2 minutes.

**Table 2** Setting a role
Task	Role Authorization
Setting the Hive administrator permission	In the Configure Resource Permission table, choose Name of the desired cluster > Hive and select Hive Admin Privilege. NOTE: After being bound to the Hive administrator role, perform the following operations during each maintenance operation: Log in to the node where the Hive client is installed as the client installation user. Run the following command to configure environment variables: For example, if the Hive client installation directory is /opt/hiveclient, run source /opt/hiveclient/bigdata_env. Run the following command to authenticate the user: kinit Hive service user Run the following command to log in to the client tool: beeline Run the following command to update the administrator permissions: set role admin;
Setting the permission to query a table of another user in the default database	In the Configure Resource Permission table, choose Name of the desired cluster > Hive > Hive Read Write Privileges. Click the name of the specified database in the database list. Tables in the database are displayed. In the Rights column of the specified table, choose Select.
Setting the permission to query a table of another user in the default database	In the Configure Resource Permission table, choose Name of the desired cluster > Hive > Hive Read Write Privileges. Click the name of the specified database in the database list. Tables in the database are displayed. In the Permission column of the specified table, select INSERT.
Setting the permission to import data to a table of another user in the default database	In the Configure Resource Permission table, choose Name of the desired cluster > Hive > Hive Read Write Privileges. Click the name of the specified database in the database list. Tables in the database are displayed. In the Permission column of the specified indexes, select DELETE and INSERT.
Setting the permission to submit HQL commands to Yarn for execution	The HQL commands used by some services are converted into MapReduce tasks and submitted to Yarn for execution. You need to set the Yarn permissions. For example, the HQL statements to be run use statements, such as insert, count, distinct, group by, order by, sort by, or join. In the Permission table, choose Name of the desired cluster > Yarn > Scheduling Queue > root. In the Permission column of the default queue, select Submit.