Step 1: Stop all Hive Processes and Daemons

  Warning: You must make sure no Hive processes are running. If Hive processes are running during the upgrade, the new version will not work correctly.

1. Stop any HiveServer processes that are running:

   $ sudo service hive-server stop 

2. Stop any HiveServer2 processes that are running:

   $ sudo service hive-server2 stop 

3. Stop the metastore:

   $ sudo service hive-metastore stop 

Step 2: Install the new Hive version on all hosts (Hive servers and clients)

See Installing Hive

Step 3: Verify that the Hive Metastore is Properly Configured

See Configuring the Hive Metastore for CDH for detailed instructions.

Step 4: Upgrade the Metastore Schema

  Important:

• Cloudera recommends that you make a backup copy of your metastore database before running the schematool or the upgrade scripts. You might need this backup copy if there are problems during the upgrade or if you need to downgrade to a previous version.
• You must upgrade the metastore schema to the version corresponding to the new version of Hive before starting Hive after the upgrade. Failure to do so may result in metastore corruption.

To upgrade the Hive metastore schema, you can use either the Hive schematool or use the schema upgrade scripts that are provided with the Hive package. Cloudera recommends that you use the schematool.

Using Hive schematool (Recommended):

$ schematool -dbType mysql -passWord <db_user_pswd> -upgradeSchemaFrom
  0.13.1 -userName <db_user_name>
Metastore connection URL:
jdbc:mysql://<cluster_address>:3306/<user_name>?useUnicode=true&characterEncoding=UTF-8
Metastore Connection Driver : com.mysql.jdbc.Driver
Metastore connection User: <user_name>
Starting upgrade metastore schema from version 0.13.1 to <new_version>
Upgrade script upgrade-0.13.1-to-<new_version>.mysql.sql
Completed pre-0-upgrade-0.13.1-to-<new_version>.mysql.sql
Completed upgrade-0.13.1-to-<new_version>.mysql.sql
schemaTool completed
          

  Note: The upgradeSchemaFrom option requires the Hive version and not the CDH version. See CDH 5 Packaging and Tarball Information for information about which Hive version ships with each CDH release.

Using Schema Upgrade Scripts:

Navigate to the directory where the schema upgrade scripts are located:

• If you installed CDH with parcels, the scripts are in the following location:

  /opt/cloudera/parcels/CDH/lib/hive/scripts/metastore/upgrade/<database_name>
                    

• If you installed CDH with packages, the scripts are in the following location:

  /usr/lib/hive/scripts/metastore/upgrade/<database_name>
                    

For example, if your Hive metastore is MySQL and you installed CDH with packages, navigate to /usr/lib/hive/scripts/metastore/upgrade/mysql.

Run the appropriate schema upgrade scripts in order. Start with the script for your database type and Hive version, and run all subsequent scripts.

For example, if you are currently running Hive 0.13.1 with MySQL and upgrading to Hive 1.1.0, start with the script for 0.13.0 to 0.14.0 for MySQL, and then run the script for Hive 0.14.0 to 1.1.0.

  Important: If there are scripts with file names that start with pre-, like pre-0-upgrade-1.1.0-to-1.1.0-cdh5.12.0.<database_type>.sql, run them before running the script without pre- in the name. For example, if you are upgrading to CDH 5.12, run pre-0-upgrade-1.1.0-to-1.1.0-cdh5.12.0 before you run upgrade-1.1.0-to-1.1.0-cdh5.12.0.<database_type>.sql.

For more information about using the scripts to upgrade the schema, see the README in the directory with the scripts.

Step 5: Start the Metastore, HiveServer2, and Beeline

See:

• Starting the Hive Metastore in CDH
• Starting, Stopping, and Using HiveServer2 in CDH

The upgrade is now complete.

Troubleshooting: If you failed to upgrade the metastore

If you failed to upgrade the metastore as instructed above, proceed as follows.

1. Identify the problem.
   The symptoms are as follows:

   • Hive stops accepting queries.
   • In a cluster managed by Cloudera Manager, the Hive Metastore canary fails.
   • An error such as the following appears in the Hive Metastore Server logs:

     Hive Schema version 0.13.0 does not match metastore's schema version 0.12.0 Metastore is not upgraded or corrupt.

2. Resolve the problem.
   If the problem you are having matches the symptoms just described, do the following:

   1. Stop all Hive services; for example:

      $ sudo service hive-server2 stop
      $ sudo service hive-metastore stop

   2. Run the Hive schematool, as instructed here.
      Make sure the value you use for the -upgradeSchemaFrom option matches the version you are currently running (not the new version). For example, if the error message in the log is

      Hive Schema version 0.13.0 does not match metastore's schema version 0.12.0 Metastore is not upgraded or corrupt.

      then the value of -upgradeSchemaFrom must be 0.12.0.
   3. Restart the Hive services you stopped.