Running Apache Hive with Alluxio
- Configure Hive
- 1 Use Alluxio as One Option to Store Hive Tables
- Create New Tables from Alluxio Files
- Map Existing Tables Stored in HDFS to Alluxio
- 2 Use Alluxio as the Default Filesystem
This guide describes how to run Apache Hive with Alluxio, so that you can easily store Hive tables in Alluxio’s tiered storage.
Please Download Hive.
To run Hive on Hadoop MapReduce, please also follow the instructions in running MapReduce on Alluxio to make sure Hadoop MapReduce can run with Alluxio.
We recommend you to download the tarball from
Alluxio download page.
Alternatively, advanced users can choose to compile this client jar from the source code
by following Follow the instructs here.
The Alluxio client jar can be found at
HIVE_AUX_JARS_PATH either in shell or
1 Use Alluxio as One Option to Store Hive Tables
There are different ways to integrate Hive with Alluxio. This section talks about how to use Alluxio as one of the filesystems (like HDFS) to store Hive tables. These tables can be either internal (managed) or external, either new tables to create or tables alreay exist in HDFS. The next section talks about how to use Alluxio as the default file system for Hive. In the following sections, Hive is running on Hadoop MapReduce in this documentation.
Tips：All the following Hive CLI examples are also applicable to Hive Beeline. You can try these commands out in Beeline shell.
Create New Tables from Alluxio Files
Hive can create new tables from files stored on Alluxio. The setup is fairly straightforward and the change is also isolated from other Hive tables. An example use case is to store frequently used Hive tables in Alluxio for high throughput and low latency by serving these files from memory storage.
Example: Create a New Internal Table
Here is an example to create an internal table in Hive backed by files in Alluxio.
You can download a data file (e.g.,
Unzip this file and upload the file
ml-100k/ on Alluxio:
$ bin/alluxio fs mkdir /ml-100k $ bin/alluxio fs copyFromLocal /path/to/ml-100k/u.user alluxio://master_hostname:port/ml-100k
Then create a new internal table:
hive> CREATE TABLE u_user ( userid INT, age INT, gender CHAR(1), occupation STRING, zipcode STRING) ROW FORMAT DELIMITED FIELDS TERMINATED BY '|' LOCATION 'alluxio://master_hostname:port/ml-100k';
Example: Create a New External Table
Make the same setup as the previous example, and create a new external table:
hive> CREATE EXTERNAL TABLE u_user ( userid INT, age INT, gender CHAR(1), occupation STRING, zipcode STRING) ROW FORMAT DELIMITED FIELDS TERMINATED BY '|' LOCATION 'alluxio://master_hostname:port/ml-100k';
The difference is that Hive will manage the lifecycle of internal tables. When you drop an internal table, Hive deletes both the table metadata and the data file from Alluxio.
Now you can query the created table. For example:
hive> select * from u_user;
Map Existing Tables Stored in HDFS to Alluxio
When Hive is already serving and managing the tables stored in HDFS,
Alluxio can also serve them for Hive if HDFS is mounted as the under storage of Alluxio.
In this example, we assume a HDFS cluster is mounted as the under storage of
Alluxio root directory (i.e., property
is set in
conf/alluxio-site.properties). Please refer to
unified namespace for more details about mount operation.
Example: Move an Internal Table from HDFS to Alluxio
We assume that the
hive.metastore.warehouse.dir property is set to
is the default value, and the internal table is already created like this:
hive> CREATE TABLE u_user ( userid INT, age INT, gender CHAR(1), occupation STRING, zipcode STRING) ROW FORMAT DELIMITED FIELDS TERMINATED BY '|'; hive> LOAD DATA LOCAL INPATH '/path/to/ml-100k/u.user' OVERWRITE INTO TABLE u_user;
The following HiveQL statement will change the table data location from HDFS to Alluxio：
hive> alter table u_user set location "alluxio://master_hostname:port/user/hive/warehouse/u_user";
Verify whether the table location is set correctly:
hive> desc formatted u_user;
Note that, accessing files in
alluxio://master_hostname:port/user/hive/warehouse/u_user for the
first time will be translated to access corresponding files in
hdfs://namenode:port/user/hive/warehouse/u_user (the default Hive internal data storage); once
the data is cached in Alluxio, Alluxio will serve them for follow-up queries without loading data
again from HDFS. The entire process is transparent to Hive and users.
Example: Move an External Table from HDFS to Alluxio
Assume there is an existing external table
u_user in Hive with location set to
You can use the following HiveQL statement to check its “Location” attribute:
hive> desc formatted u_user;
Then use the following HiveQL statement to change the table data location from HDFS to Alluxio：
hive> alter table u_user set location "alluxio://master_hostname:port/ml-100k";
Example: Move an Alluxio Table Back to HDFS
In both cases above about changing table data location to Alluxio, you can also change the table location back to HDFS:
hive> alter table TABLE_NAME set location "hdfs://namenode:port/table/path/in/HDFS";
Instructions and examples till here illustrate how to use Alluxio as one of the filesystems to store tables in Hive, together with other filesystems like HDFS. They do not require to change the global setting in Hive such as the default filesystem which is covered in the next section.
2 Use Alluxio as the Default Filesystem
Apache Hive can also use Alluxio through a generic file system interface to replace the Hadoop file system. In this way, the Hive uses Alluxio as the default file system and its internal metadata and intermediate results will be stored in Alluxio by default.
Add the following property to
hive-site.xml in your Hive installation
<property> <name>fs.defaultFS</name> <value>alluxio://master_hostname:port</value> </property>
To use fault tolerant mode, set the Alluxio cluster properties appropriately (see example below) in
alluxio-site.properties file which is on the classpath.
Alternatively you can add the properties to the Hive
hive-site.xml configuration which is then
propagated to Alluxio.
<configuration> <property> <name>alluxio.zookeeper.enabled</name> <value>true</value> </property> <property> <name>alluxio.zookeeper.address</name> <value>[zookeeper_hostname]:2181</value> </property> </configuration>
Add additional Alluxio site properties to Hive
If there are any Alluxio site properties you want to specify for Hive, add those to
to Hadoop configuration directory on each node. For example, change
alluxio.user.file.writetype.default from default
<property> <name>alluxio.user.file.writetype.default</name> <value>CACHE_THROUGH</value> </property>
Using Alluxio with Hive
Create Directories in Alluxio for Hive:
$ ./bin/alluxio fs mkdir /tmp $ ./bin/alluxio fs mkdir /user/hive/warehouse $ ./bin/alluxio fs chmod 775 /tmp $ ./bin/alluxio fs chmod 775 /user/hive/warehouse
Then you can follow the Hive documentation to use Hive.
Example: Create a Table
Create a table in Hive and load a file in local path into Hive:
Again use the data file in
http://grouplens.org/datasets/movielens/ as an example.
hive> CREATE TABLE u_user ( userid INT, age INT, gender CHAR(1), occupation STRING, zipcode STRING) ROW FORMAT DELIMITED FIELDS TERMINATED BY '|' STORED AS TEXTFILE; hive> LOAD DATA LOCAL INPATH '/path/to/ml-100k/u.user' OVERWRITE INTO TABLE u_user;
View Alluxio WebUI at
http://master_hostname:port and you can see the directory and file Hive
Using a single query:
hive> select * from u_user;
And you can see the query results from console: