Hive ACID Data Source for Apache Spark
A Datasource on top of Spark Datasource V1 APIs, that provides Spark support for Hive ACID transactions.
This datasource provides the capability to work with Hive ACID V2 tables, both Full ACID tables as well as Insert-Only tables. Currently, it supports reading from these ACID tables only, and ability to write will be added in the near future.
These are the pre-requisites to using this library:
- You already have Hive ACID tables (ACID V2) and need to read it from Spark (as currently write is not NOT supported).
- You have Hive Metastore DB with version 3.0.0 or higher. Please refer to Hive Metastore for details.
- You have a Hive Metastore Server running with version 3.0.0 or higher, as Hive ACID needs a standalone Hive Metastore Server to operate. Please refer to Hive Configuration for configuration options.
- You are using the above Hive Metastore Server with your Spark for its metastore communications.
Change configuration in
$SPARK_HOME/conf/hive-site.xml to point to already configured HMS server endpoint. If you meet the above pre-requisites, this is probably already configured.
<configuration> <property> <name>hive.metastore.uris</name> <!-- hostname must point to the Hive metastore URI in your cluster --> <value>thrift://hostname:10000</value> <description>URI for spark to contact the hive metastore server</description> </property> </configuration>
There are a few ways to use the library while running spark-shell
Use the published package
spark-shell --packages qubole:spark-acid:0.4.0-s_2.11
If you built the jar yourself, copy the
To read the acid table from Scala / pySpark, the table can be directly accessed using this datasource.
Note the short name of this datasource is
scala> val df = spark.read.format("HiveAcid").options(Map("table" -> "default.acidtbl")).load() scala> df.collect()
To read an existing Hive acid table through pure SQL, you need to create a dummy table that acts as a symlink to the original acid table. This symlink is required to instruct Spark to use this datasource against an existing table.
To create the symlink table
scala> spark.sql("create table symlinkacidtable using HiveAcid options ('table' 'default.acidtbl')")
NB: This will produce a warning indicating that Hive does not understand this format
WARN hive.HiveExternalCatalog: Couldn’t find corresponding Hive SerDe for data source provider com.qubole.spark.datasources.hiveacid.HiveAcidDataSource. Persisting data source table `default`.`sparkacidtbl` into Hive metastore in Spark SQL specific format, which is NOT compatible with Hive.
Please ignore it, as this is a sym table for Spark to operate with and no underlying storage.
To read the table data:
scala> var df = spark.sql("select * from symlinkacidtable") scala> df.collect()
ACID datasource is published spark-packages.org. The latest version of the binary is
Compatibility with Apache Spark Versions
ACID datasource has been tested to work with Apache Spark 2.4.3, but it should work with older versions as well. However, because of a Hive dependency, this datasource needs Hadoop version 2.8.2 or higher due to HADOOP-14683
NB: Hive ACID V2 is supported in Hive 3.0.0 onwards and for that hive Metastore db needs to be upgraded to 3.0.0 or above.
Data Storage Compatibility
ACID datasource does not control data storage format and layout, which is managed by Hive. It works with data written by Hive version 3.0.0 and above. Please see Hive ACID storage layout.
ACID datasource works with data stored on local files, HDFS as well as cloud blobstores (AWS S3, Azure Blob Storage etc).
- First, build the dependencies and publish it to local. The shaded-dependencies sub-project is an sbt project to create the shaded hive metastore and hive exec jars combined into a fat jar
spark-acid-shaded-dependencies. This is required due to our dependency on Hive 3 for Hive ACID, and Spark currently only supports Hive 1.2
To compile and publish shaded dependencies jar:
cd shaded-dependencies sbt clean publishLocal
Next, build the main project:
cd ../ sbt assembly
This will create the
spark-acid-assembly-0.4.0.jar which can be now used in your application.
Tests are run against a standalone docker setup. Please refer to [Docker setup] (docker/README.md) to build and start a container.
NB: Container run HMS server, HS2 Server and HDFS and listens on port 10000,10001 and 9000 respectively. So stop if you are running HMS or HDFS on same port on host machine.
To run the full integration test:
To release a new version use
To publish a new version use
Read more about sbt release
Hive ACID works with locks, where every client that is operating on ACID tables is expected to acquire locks for the duration of reads and writes. This datasource however does not acquire read locks. When it needs to read data, it talks to the HiveMetaStore Server to get the list of transactions that have been committed, and using that, the list of files it should read from the filesystem. But it does not lock the table or partition for the duration of the read.
Because it does not acquire read locks, there is a chance that the data being read could get deleted by Hive's ACID management(perhaps because the data was ready to be cleaned up due to compaction). To avoid this scenario which can read to query failures, we recommend that you disable automatic compaction and cleanup in Hive on the tables that you are going to be reading using this datasource, and recommend that the compaction and cleanup be done when you know that no users are reading those tables. Ideally, we would have wanted to just disable automatic cleanup and let the compaction happen, but there is no way in Hive today to just disable cleanup and it is tied to compaction, so we recommend to disable compaction.
You have a few options available to you to disable automatic compaction:
Disable automatic compaction globally, i.e. for all ACID tables: To do this, we recommend you set the following compaction thresholds on the Hive Metastore Server to a very high number(like 1000000 below) so that compaction never gets initiated automatically and can only be initiated manually.
Disable automatic compaction for selected ACID tables: To do this, you can set a table property using the ALTER TABLE command:
ALTER TABLE <> SET TBLPROPERTIES ("NO_AUTO_COMPACTION"="true")
This will disable automatic compaction on a particular table, and you can use this approach if you have a limited set of ACID tables that you intend to access using this datasource.
Once you have disabled automatic compaction either globally or on a particular set of tables, you can chose to run compaction manually at a desired time when you know there are no readers reading these acid tables, using an ALTER TABLE command:
ALTER TABLE table_name [PARTITION (partition_key = 'partition_value' [, ...])] COMPACT 'compaction_type'[AND WAIT] [WITH OVERWRITE TBLPROPERTIES ("property"="value" [, ...])];
compaction_type are either
More details on the above commands and their variations available here.
We are looking into removing this restriction, and hope to be able to fix this in the near future.
We use Github Issues to track issues.
Reporting bugs or feature requests
Please use the github issues for the spark-acid project to report issues or raise feature requests.