Skip to content

Latest commit

 

History

History
120 lines (84 loc) · 7.51 KB

README.md

File metadata and controls

120 lines (84 loc) · 7.51 KB
Raw

Hive Connector

This project is a library to make Hive read Delta tables. The project provides a uber JAR delta-hive-assembly_<scala_version>-<delta_connectors_version>.jar to use in Hive. You can use either Scala 2.11, 2.12 or 2.13. The released JARs are available in the releases page. Please download the uber JAR for the corresponding Scala version you would like to use.

You can also use the following instructions to build it as well.

Build the uber JAR

Please skip this section if you have downloaded the connector JARs.

  • To compile the project, run build/sbt hive/compile
  • To run Hive 3 tests, run build/sbt hiveMR/test hiveTez/test
  • To run Hive 2 tests, run build/sbt hive2MR/test hive2Tez/test
  • To generate the uber JAR that contains all libraries needed for Hive, run build/sbt hiveAssembly/assembly

The above commands will generate the following JAR, for latest Delta Connectors version x.y.z:

hive/target/scala-2.12/delta-hive-assembly_2.12-x.y.z.jar

This uber JAR includes the Hive connector and all its dependencies. They need to be put in Hive’s classpath.

Note: if you would like to build using Scala 2.11, you can run the SBT command build/sbt "++ 2.11.12 hiveAssembly/assembly" to generate the following JAR:

hive/target/scala-2.11/delta-hive-assembly_2.11-x.y.z.jar

Setting up Hive

This section describes how to set up Hive to load the Delta Hive connector.

Configure Input Formats

Before starting your Hive CLI or running your Hive script, add the following special Hive config to the hive-site.xml file. (Its location is /etc/hive/conf/hive-site.xml in an EMR cluster).

<property>
  <name>hive.input.format</name>
  <value>io.delta.hive.HiveInputFormat</value>
</property>
<property>
  <name>hive.tez.input.format</name>
  <value>io.delta.hive.HiveInputFormat</value>
</property>

Alternatively, you can also run the following SQL commands in Hive CLI before reading Delta tables to set io.delta.hive.HiveInputFormat:

SET hive.input.format=io.delta.hive.HiveInputFormat;
SET hive.tez.input.format=io.delta.hive.HiveInputFormat;

Add Hive uber JAR

The second step is to upload the above uber JAR to the machine that runs Hive. Next, make the JAR accessible to Hive. There are several ways to do this, listed below. To verify that the JAR was properly added, run LIST JARS; in the Hive CLI.

  • in the Hive CLI, run ADD JAR <path-to-jar>;
  • add the uber JAR to a folder already pointed to by the HIVE_AUX_JARS_PATH environmental variable
  • modify the same hive-site.xml file as above, and add the following. (Note that this has to be done before you start the Hive CLI)
<property>
  <name>hive.aux.jars.path</name>
  <value>path_to_uber_jar</value>
</property>
  • add the path of the uber JAR to Hive’s environment variable, HIVE_AUX_JARS_PATH. You can find this environment variable in the hive-env.sh file, whose location is /etc/hive/conf/hive-env.sh on an EMR cluster. This setting will tell Hive where to find the connector JAR. Ensure you source the script with source /etc/hive/conf/hive-env.sh.

Create a Hive table

After finishing setup, you should be able to create a Delta table in Hive.

Right now the connector supports only EXTERNAL Hive tables. The Delta table must be created using Spark before an external Hive table can reference it.

Here is an example of a CREATE TABLE command that defines an external Hive table pointing to a Delta table on s3://foo-bucket/bar-dir.

CREATE EXTERNAL TABLE deltaTable(col1 INT, col2 STRING)
STORED BY 'io.delta.hive.DeltaStorageHandler'
LOCATION '/delta/table/path'

io.delta.hive.DeltaStorageHandler is the class that implements Hive data source APIs. It will know how to load a Delta table and extract its metadata. The table schema in the CREATE TABLE statement must be consistent with the underlying Delta metadata. Otherwise, the connector will throw an error to tell you about the inconsistency.

Specifying paths in LOCATION

/delta/table/path in LOCATION is a normal path. If there is no scheme in the path, it will use the default file system specified in your Hadoop configuration. You can add an explicit scheme to specify which file system you would like to use, such as file:///delta/table/path, s3://your-s3-bucket/delta/table/path.

Frequently asked questions (FAQ)

Supported Hive versions

Hive 2.x and 3.x.

Can I use this connector in Apache Spark or Presto?

No. The connector must be used with Apache Hive. It doesn't work in other systems, such as Apache Spark or Presto.

If I create a table using the connector in Hive, can I query it in Apache Spark or Presto?

No. The table created by this connector in Hive cannot be read in any other systems right now. We recommend to create different tables in different systems but point to the same path. Although you need to use different table names to query the same Delta table, the underlying data will be shared by all of systems.

If a table in the Hive Metastore is created by other systems such as Apache Spark or Presto, can I use this connector to query it in Hive?

No. If a table in the Hive Metastore is created by other systems such as Apache Spark or Presto, Hive cannot find the correct connector to read it. You can follow our instruction to create a new table with a different table name but point to the same path in Hive. Although it's a different table name, the underlying data will be shared by all of systems. We recommend to create different tables in different systems but point to the same path.

Can I write to a Delta table using this connector?

No. The connector doesn't support writing to a Delta table.

Do I need to specify the partition columns when creating a Delta table?

No. The partition columns are read from the underlying Delta metadata. The connector will know the partition columns and use this information to do the partition pruning automatically.

Why do I need to specify the table schema? Shouldn’t it exist in the underlying Delta table metadata?

Unfortunately, the table schema is a core concept of Hive and Hive needs it before calling the connector.

What if I change the underlying Delta table schema in Spark after creating the Hive table?

If the schema in the underlying Delta metadata is not consistent with the schema specified by CREATE TABLE statement, the connector will report an error when loading the table and ask you to fix the schema. You must drop the table and recreate it using the new schema. Hive 3.x exposes a new API to allow a data source to hook ALTER TABLE. You will be able to use ALTER TABLE to update a table schema when the connector supports Hive 3.x.

Hive has three execution engines, MapReduce, Tez and Spark. Which one does this connector support?

The connector supports MapReduce and Tez. It doesn't support Spark execution engine in Hive.