Installation from Tarball

Server Installation from Source

Prerequisites

• machine to put the installation tar on
• machine on which the server can be installed — this should have access to the Hadoop cluster in question, and be accessible from the machines you launch jobs from
• an RDBMS — we recommend MySQL and provide instructions for it
• Hadoop cluster
• Unix user that the server will run as, and, if you are running your cluster in secure mode, an associated Kerberos service principal and keytabs.

Throughout these instructions when you see a word in italics it indicates a place where you should replace the word with a locally appropriate value such as a hostname or password.

Tarball Location

A binary tarball for HCatalog 0.11.0 is provided in the build directory:

build/hcatalog-0.11.0.x.x.x.x-xxx.tar.gz

If it is in another location, move it to the HCatalog build directory.

Database Setup

If you do not already have Hive installed with MySQL, the following will walk you through how to do so. If you have already set this up, you can skip this step.

Select a machine to install the database on. This need not be the same machine as the Thrift server, which we will set up later. For large clusters we recommend that they not be the same machine. For the purposes of these instructions we will refer to this machine as hivedb.acme.com.

Install MySQL server on hivedb.acme.com. You can obtain packages for MySQL from MySQL's download site. We have developed and tested with versions 5.1.46 and 5.1.48. We suggest you use these versions or later. Once you have MySQL up and running, use the mysql command line tool to add the hive user and hivemetastoredb database. You will need to pick a password for your hive user, and replace dbpassword in the following commands with it.

mysql -u root
mysql> CREATE USER 'hive'@'hivedb.acme.com' IDENTIFIED BY 'dbpassword';
mysql> CREATE DATABASE hivemetastoredb DEFAULT CHARACTER SET latin1 DEFAULT COLLATE latin1_swedish_ci;
mysql> GRANT ALL PRIVILEGES ON hivemetastoredb.* TO 'hive'@'hivedb.acme.com' WITH GRANT OPTION;
mysql> flush privileges;
mysql> quit;

Use the database installation script found in the Hive package to create the database. In the line below, hive_home refers to the directory where you have installed Hive. If you are using Hive rpms, then this will be /usr/lib/hive.

mysql -u hive -D hivemetastoredb -hhivedb.acme.com -p < hive_home/scripts/metastore/upgrade/mysql/hive-schema-0.11.0.mysql.sql

Thrift Server Setup

If you do not already have Hive running a metastore server using Thrift, you can use the following instructions to set up and run one. You may skip this step if you already are using a Hive metastore server.

Select a machine to install your Thrift server on. For smaller and test installations this can be the same machine as the database. For the purposes of these instructions we will refer to this machine as hcatsvr.acme.com.

If you have not already done so, install Hive 0.11.0 on this machine. You can use the binary distributions provided by Hive or rpms available from Apache Bigtop. If you use the Apache Hive binary distribution, select a directory, henceforth referred to as hive_home, and untar the distribution there. If you use the rpms, hive_home will be /usr/lib/hive.

Install the MySQL Java connector libraries on hcatsvr.acme.com. You can obtain these from MySQL's download site.

Select a user to run the Thrift server as. This user should not be a human user, and must be able to act as a proxy for other users. We suggest the name "hive" for the user. Throughout the rest of this documentation we will refer to this user as hive. If necessary, add the user to hcatsvr.acme.com.

Select a root directory for your installation of HCatalog. This directory must be owned by the hive user. We recommend /usr/local/hive. If necessary, create the directory. You will need to be the hive user for the operations described in the remainder of this Thrift Server Setup section.

Copy the HCatalog installation tarball into a temporary directory, and untar it. Then change directories into the new distribution and run the HCatalog server installation script. You will need to know the directory you chose as root and the directory you installed the MySQL Java connector libraries into (referred to in the command below as dbroot). You will also need your hadoop_home, the directory where you have Hadoop installed, and the port number you wish HCatalog to operate on which you will use to set portnum.

tar zxf hcatalog-0.11.0.x.x.x.x-xxx.tar.gz
cd hcatalog-0.11.0.x.x.x.x-xxx
share/hcatalog/scripts/hcat_server_install.sh -r root -d dbroot -h hadoop_home -p portnum

Now you need to edit your hive_home/conf/hive-site.xml file. If there is no such file in the hive conf directory, copy hcat_home/etc/hcatalog/proto-hive-site.xml and rename it hive-site.xml in hive_home/conf/. Open this file in your favorite text editor. The following table shows the values you need to configure.

You can now proceed to starting the server.

Starting the Server

To start your server, HCatalog needs to know where Hive is installed. This is communicated by setting the environment variable HIVE_HOME to the location you installed Hive. Start the HCatalog server by switching directories to root and invoking "HIVE_HOME=hive_home sbin/hcat_server.sh start".

Logging

Server activity logs are located in root/var/log/hcat_server. Logging configuration is located at root/conf/log4j.properties. Server logging uses DailyRollingFileAppender by default. It will generate a new file per day and does not expire old log files automatically.

Stopping the Server

To stop the HCatalog server, change directories to the root directory and invoke "HIVE_HOME=hive_home sbin/hcat_server.sh stop".

Client Installation

Select a root directory for your installation of HCatalog client. We recommend /usr/local/hcat. If necessary, create the directory.

Copy the HCatalog installation tarball into a temporary directory, and untar it.

tar zxf hcatalog-0.11.0.x.x.x.x-xxx.tar.gz

Now you need to edit your hive_home/conf/hive-site.xml file. You can use the same file as on the server except that the value of javax.jdo.option.ConnectionPasswordh should be removed. This avoids having the password available in plain text on all of your clients.

The HCatalog command line interface (CLI) can now be invoked as HIVE_HOME=hive_home root/bin/hcat.