Skip to main content

Using MySQL as a Hive backend database

By Anonymous
Listen:

Hive let us use a SQL like (HiveQL) style to analyse large datasets with ad-hoc queries, and comes as a service on top of hdfs. It is easy to use and most SQL programmers can instant write some queries.
The lack of the installation are the included derby DB, which is running on the node locally. For that Hive is not really multiuser-capable.

To use Hive with more than one user you have to setup a backend database. The database will hold all metainformations regarding your tables, partitions, splits and rows. For that the database should be safe (maybe replication) or a HVA installation. I use 2 MySQL servers in a ESX Cluster environment with enabled binary logs (Active/Standby).

Setup a server and install mysql-server version 5.1 and up. To get absolute safe you can setup a MySQL cluster ;) Let us configure the mysql-database:

# cat /etc/my.cnf
[mysqld_safe]
socket      = /var/lib/mysql/mysql.sock
[mysqld]
user        = mysql
pid-file    = /var/run/mysqld/mysqld.pid
socket      = /var/lib/mysql/mysql.sock
log-error   = /var/log/mysqld.log
datadir     = /opt/hadoop/mysql
default-storage_engine  = InnoDB
skip-bdb                = 1
old_passwords           = 0
skip_name_resolve
connect_timeout     = 30
wait_timeout        = 30
interactive_timeout = 100
key_buffer          = 128M
thread_concurrency  = 4
thread_cache        = 16
thread_stack        = 256K
table_cache         = 512
tmp_table_size      = 64M
max_heap_table_size = 64M
server-id           = 1001
log_bin             = /var/log/mysql/mysqlserver-bin.log
expire_logs_days    = 3
max_binlog_size     = 256M
innodb_file_per_table           = 1
innodb_data_file_path           = ibdata1:10M:autoextend
innodb_buffer_pool_size         = 512M
innodb_log_file_size            = 16M
innodb_flush_log_at_trx_commit  = 1
long_query_time     = 2
log_slow_queries    = /var/log/mysql/mysql-slow.log
query_cache_size    = 64M
query_cache_type    = 1
query_cache_limit   = 4M

You see, we use binary logging, as engine InnoDB (no locking tables) and some RAM related params. Consult the mysql manual for a complete description (would be a larger post).

Restart your mysqlserver (service mysqld restart). Now create the user and table:
mysql> CREATE USER 'USER'@'%' IDENTIFIED BY 'PASSWORD';
mysql> GRANT ALL PRIVILEGES ON *.* TO 'USER'@'%' WITH GRANT OPTION;
mysql> create DATABASE hive-live;

Thats all. I know, very low security. But the server should only hold one database.

Setup hive to use the metastore and add in hive-default.xml:
# vi /etc/hive/conf/hive-default.xml
<!-- add mysql metastore -->
<property>
  <name>javax.jdo.option.ConnectionURL</name>
  <value>jdbc:mysql://mysqlserver:3306/hive_live_new?createDatabaseIfNotExist=true</value>
</property>
<property>
  <name>javax.jdo.option.ConnectionDriverName</name>
  <value>com.mysql.jdbc.Driver</value>
</property>
<property>
  <name>javax.jdo.option.ConnectionUserName</name>
  <value>USER</value>
</property>
<property>
  <name>javax.jdo.option.ConnectionPassword</name>
  <value>PASSWORD</value>
</property>
<!-- end -->

To get Hive running with the mysql-driver, you have to download them [1] and copy across your cluster:
for i in $(cat /etc/hadoop-0.20/conf/slaves); do scp -r /usr/lib/hive/lib/mysql-connector-java-5.1.11-bin.jar $i:/usr/lib/hive/lib/; done

Now copy the hive-config too:
for i in $(cat /etc/hadoop-0.20/conf/slaves); do scp -r /etc/hive/conf/hive-* $i:/etc/hive/conf.dist/; done

Thats all. If you use hive now the first statement should take a while, because hive will create the schema at the backend. Let us check:

mysql> use hive_live;
mysql> show tables;
+-------------------------+
| Tables_in_hive_live     |
+-------------------------+
| BUCKETING_COLS          |
| COLUMNS                 |
| DATABASE_PARAMS         |
| DBS                     |
| DB_PRIVS                |
| GLOBAL_PRIVS            |
| IDXS                    |
| INDEX_PARAMS            |
| PARTITIONS              |
| PARTITION_KEYS          |
| PARTITION_KEY_VALS      |
| PARTITION_PARAMS        |
| PART_COL_PRIVS          |
| PART_PRIVS              |
| ROLES                   |
| ROLE_MAP                |
| SDS                     |
| SD_PARAMS               |
| SEQUENCE_TABLE          |
| SERDES                  |
| SERDE_PARAMS            |
| SORT_COLS               |
| TABLE_PARAMS            |
| TBLS                    |
| TBL_COL_PRIVS           |
| TBL_PRIVS               |
| TYPES                   |
| TYPE_FIELDS             |
+-------------------------+
28 rows in set (0.01 sec)

If you have to ugrade the schema (hive-update maybe), don't be worry. Hive comes with SQL-statements, take a look at /var/lib/hive/metastore/scripts/upgrade/mysql/. To apply a schema cd into the directory and open mysql-cli:
mysql> source /var/lib/hive/metastore/scripts/upgrade/mysql/hive-schema-0.7.0.mysql.sql <enter>

The script will load all sql-statements they will need to upgrade the database. A good idea is a full DB backup before.


[1] http://dev.mysql.com/downloads/connector/j/
Labels:

Comments

Post a Comment

Popular posts from this blog

Why Is Customer Obsession Disappearing?

By
 It's wild that even with all the cool tech we've got these days, like AI solving complex equations and doing business across time zones in a flash, so many companies are still struggling with the basics: taking care of their customers.The drama around Coinbase's customer support is a prime example of even tech giants messing up. And it's not just Coinbase — it's a big-picture issue for the whole industry. At some point, the idea of "customer obsession" got replaced with "customer automation," and now we're seeing the problems that came with it. "Cases" What Not to Do Coinbase, as main example, has long been synonymous with making cryptocurrency accessible. Whether you’re a first-time buyer or a seasoned trader, their platform was once the gold standard for user experience. But lately, their customer support practices have been making headlines for all the wrong reasons: Coinbase - Stuck in the Loop:  Users have reported being caugh...
Post a Comment
Read more

MySQL Scaling in 2024

By
When your MySQL database reaches its performance limits, vertical scaling through hardware upgrades provides a temporary solution. Long-term growth, though, requires a more comprehensive approach. This involves optimizing the database strategically and integrating complementary technologies. Caching The implementation of a caching layer, such as Memcached or Redis , can result in a notable reduction in the load and an increase ni performance at MySQL. In-memory stores cache data that is accessed frequently, enabling near-instantaneous responses and freeing the database for other tasks. For applications with heavy read traffic on relatively static data (e.g. product catalogues, user profiles), caching represents a low-effort, high-impact solution. Consider a online shop product catalogue with thousands of items. With each visit to the website, the application queries the database in order to retrieve product details. By using caching, the retrieved details can be stored in Memcached (a...
Post a Comment
Read more

Deal with corrupted messages in Apache Kafka

By
Under some strange circumstances, it can happen that a message in a Kafka topic is corrupted. This often happens when using 3rd party frameworks with Kafka. In addition, Kafka < 0.9 does not have a lock on Log.read() at the consumer read level, but does have a lock on Log.write(). This can lead to a rare race condition as described in KAKFA-2477 [1]. A likely log entry looks like this: ERROR Error processing message, stopping consumer: (kafka.tools.ConsoleConsumer$) kafka.message.InvalidMessageException: Message is corrupt (stored crc = xxxxxxxxxx, computed crc = yyyyyyyyyy Kafka-Tools Kafka stores the offset of each consumer in Zookeeper. To read the offsets, Kafka provides handy tools [2]. But you can also use zkCli.sh, at least to display the consumer and the stored offsets. First we need to find the consumer for a topic (> Kafka 0.9): bin/kafka-consumer-groups.sh --zookeeper management01:2181 --describe --group test Prior to Kafka 0.9, the only way to get this in...
Post a Comment
Read more