[
https://issues.apache.org/jira/browse/HIVE-5659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13806975#comment-13806975
]
Craig Condit commented on HIVE-5659:
------------------------------------
In our case, I'm not sure the best way to handle this. We have some options
(such as HBase direct reads) that require configuration parameters that would
affect all HDFS users. Those configurations would be set if we included
hbase-site.xml, and wouldn't be overridable.
It just seems like configuration in hive-site.xml should override
hbase-site.xml, and not the other way around.
> 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)
