[
https://issues.apache.org/jira/browse/HIVE-22160?focusedWorklogId=442521&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-442521
]
ASF GitHub Bot logged work on HIVE-22160:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 08/Jun/20 00:25
Start Date: 08/Jun/20 00:25
Worklog Time Spent: 10m
Work Description: github-actions[bot] commented on pull request #758:
URL: https://github.com/apache/hive/pull/758#issuecomment-640302883
This pull request has been automatically marked as stale because it has not
had recent activity. It will be closed if no further activity occurs.
Feel free to reach out on the d...@hive.apache.org list if the patch is in
need of reviews.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 442521)
Time Spent: 0.5h (was: 20m)
> Job Configuration Properties Unable to Override hive-site.xml Properties in
> Master Node
> ---------------------------------------------------------------------------------------
>
> Key: HIVE-22160
> URL: https://issues.apache.org/jira/browse/HIVE-22160
> Project: Hive
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 3.1.2
> Reporter: Haotian Zhang
> Assignee: Haotian Zhang
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When running on the master node, these two ways of creating HiveConf can
> result in different Hive configurations:
> {code:java}
> HiveConf hiveConf = HCatUtil.getHiveConf(job.getConfiguration());
> {code}
> the above one referred as Style1, and
> {code:java}
> HiveConf hiveConf = new HiveConf();
> hiveConf.addResource(job.getConfiguration());
> {code}
> the above one referred as Style2. If there are properties exist both in
> hiveSite and jobConf. For example, in hive-site.xml, we have property
> {noformat}
> hive.metastore.uris = AAA{noformat}
> And if at the same time in jobConf, such as action configurations in Oozie's
> workflow.xml, we have
> {noformat}
> hive.metastore.uris = BBB{noformat}
> Then in Style1, the "hive.metastore.uris" property in hiveConf is "AAA" and
> in Style2, the property in hiveConf is "BBB".
> Here is another example to illustrate this. Suppose in hiveSite,
> "hive.metastore.uris" is AAA and in jobConf it is BBB, when executing the
> following code:
> {code:java}
> HiveConf hiveConf = HCatUtil.getHiveConf(job.getConfiguration());
> log.info("the hive metastore uri in hiveconf first is: " +
> hiveConf.get("hive.metastore.uris"));
> hiveConf = HCatUtil.getHiveConf(job.getConfiguration());
> log.info("the hive metastore uri in hiveconf second is: " +
> hiveConf.get("hive.metastore.uris"));
> {code}
> And the log output is:
> {noformat}
> the hive metastore uri in hiveconf first is: AAA
> the hive metastore uri in hiveconf first is: BBB{noformat}
> In all, the jobConf does not got set to the configuration as expected when
> there's already such a property existed in hive site. This happen only on the
> master node but not on task nodes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
