[
https://issues.apache.org/jira/browse/HIVE-5659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13863804#comment-13863804
]
Sushanth Sowmyan commented on HIVE-5659:
----------------------------------------
While I agree with the order Nick is putting forth, and thus, a need for the
addResources to not clobber the existing set config, I have to say I balk at
the notion of putting hbase-specific config, even if associated with hbase-hive
integration inside hive-site.xml. That seems to be asking for errors arising
from messy config keeping. It can lead up to two-sources of truth if hive
treats hive's copy of hbase config as prime, and hbase server/etc that the
handler talk to treat hbase config as prime truth.
> 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.5#6160)
