Submitting a Hive Job

Scenario

This section describes how to use the Oozie client to submit a Hive job.

Hive jobs are divided into the following types:

• Hive job

  Hive job that is connected in JDBC mode

• Hive2 job

  Hive job that is connected in Beeline mode

This section describes how to submit a Hive job using the Oozie client.

• The procedure for submitting a Hive2 job using the Oozie client is the same as that for submitting a Hive job. You only need to change /Hive in the procedure to /Hive2.

  For example, if the Hive job running directory is /opt/client/Oozie/oozie-client-*/examples/apps/hive/, then the running directory of Hive2 is /opt/client/Oozie/oozie-client-*/examples/apps/hive2/.

• You are advised to download the latest client.

Prerequisites

• The Hive and Oozie components and clients have been installed and are running properly.
• You have created or obtained the human-machine account and password for accessing the Oozie service.
  

  • This user must belong to the hadoop, supergroup, and hive groups and be assigned with the Oozie role operation permission. If the multi-instance function is enabled for Hive, the user must belong to a specific Hive instance group, for example, hive3.
  • This user must also be assigned the manager_viewer role at least.
• You have obtained the URL of the Oozie server (any instance) in the running state, for example, https://10.1.130.10:21003/oozie.
• You have obtained the name of the Oozie server, for example, 10-1-130-10.
• You have obtained the IP address of the active Yarn ResourceManager, for example, 10.1.130.11.

Procedure

1. Log in to the node where the Oozie client is installed as the client installation user.
2. Run the following command to obtain the installation environment. /opt/client/ is an example client installation path.

   source /opt/client/bigdata_env

3. Check the cluster authentication mode.
   • If the cluster is in security mode, run the kinit command to authenticate users.

     For example, the oozieuser user is authenticated using the following command:

     kinit oozieuser

   • If the cluster is in normal mode, go to 4.

4. Run the following command to go to the example directory:

   cd /opt/client/Oozie/oozie-client-*/examples/apps/hive/

   Table 1 lists the files that you need to pay attention to in the directory.

   Table 1 File description

   File	Description
   hive-site.xml	Configuration file of a Hive job
   job.properties	Parameter definition file of a workflow
   script.q	SQL script of a Hive job
   workflow.xml	Rule definition file of a workflow

5. Run the following command to edit the job.properties file:

   vi job.properties

   Perform the following modifications:

   Change the value of userName to the name of the human-machine user who submits the job, for example, userName=oozieuser.

6. Run the oozie job command to run the workflow file:

   oozie job -oozie https://Host name of the Oozie role:21003/oozie/ -config job.properties -run

   

   • The command parameters are described as follows:

     -oozie URL of the Oozie server that executes a job

     -config Workflow property file

     -run Executing a workflow

   • If a job ID, for example, job: 0000021-140222101051722-oozie-omm-W, is displayed after the workflow file is executed, the job is successfully submitted. You can view the execution results on the Oozie management page.

     Log in to the Oozie web UI at https://IP address of the Oozie role:21003/oozie as user oozieuser.

     On the Oozie web UI, you can view the submitted workflow information based on the job ID in the table on the page.