[
https://issues.apache.org/jira/browse/HIVE-5659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13806894#comment-13806894
]
Ashutosh Chauhan commented on HIVE-5659:
----------------------------------------
[~ccondit] I think current behavior is correct. To achieve what you want (ie
configure hbase for hive) you should put {{hbase-site.xml}} in hive's classpath
so that hbase configs are picked up from there, instead of putting hbase
configs in hive-site.xml
> HBaseStorageHandler overwrites Hive-set HBase properties with hbase-defaults
> ----------------------------------------------------------------------------
>
> Key: HIVE-5659
> URL: https://issues.apache.org/jira/browse/HIVE-5659
> Project: Hive
> Issue Type: Bug
> Components: HBase Handler
> Affects Versions: 0.12.0
> Reporter: Craig Condit
> Attachments: HIVE-5659.patch
>
>
> As part of the changes to HIVE-5260, it appears that HBase properties set in
> hive-conf.xml are being clobbered by defaults from hbase-default.xml.
> Specifically, we noticed it when attempting to set hbase.zookeeper.quorum.
> That value defaults to 'localhost' and results in queries of HBase tables
> hanging attempting to acquire a lock from a Zookeeper instance which isn't
> running.
> Any properties set in hive-site.xml will be overwritten by those in
> hbase-default.xml, which doesn't seem good.
> The call to HBaseConfiguration.addHbaseResources(jobConf) seems to be the
> culprit, around line 337.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
