Daniel Horak created HIVE-9348:
----------------------------------
Summary: Hive Metastore didn't start with set environment variable
DEBUG
Key: HIVE-9348
URL: https://issues.apache.org/jira/browse/HIVE-9348
Project: Hive
Issue Type: Bug
Affects Versions: 0.13.0
Environment: # cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.6 (Santiago)
# rpm -q hive
hive-0.13.0.2.1.7.0-784.el6.noarch
Reporter: Daniel Horak
Priority: Minor
When I run following db schema check with env variable DEBUG set to something,
the command freeze. (This command is copied from ambari logs, see AMBARI-9085.)
{noformat}
export HIVE_CONF_DIR=/etc/hive/conf.server
DEBUG=1 /usr/lib/hive/bin/schematool -info -dbType mysql -userName hive
-passWord $PASSWORD
{noformat}
When environment variable DEBUG isn't exist (or is empty), everything works
well:
{noformat}
# DEBUG= /usr/lib/hive/bin/schematool -info -dbType mysql -userName hive
-passWord $PASSWORD
Metastore connection URL:
jdbc:mysql://HOSTNAME/hive?createDatabaseIfNotExist=true
Metastore Connection Driver : com.mysql.jdbc.Driver
Metastore connection User: hive
Hive distribution version: 0.13.0
Metastore schema version: 0.13.0
schemaTool completeted
{noformat}
Is this expected behaviour?
It might lead to unexpected behaviour in combination with Ambari and it is very
difficult to debug it (please check also jira AMBARI-9085).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
