You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Ashutosh Chauhan (JIRA)" <ji...@apache.org> on 2017/11/10 01:39:00 UTC
[jira] [Updated] (HIVE-16075) MetaStore needs to reinitialize log4j
to allow log specific settings via hiveconf take effect
[ https://issues.apache.org/jira/browse/HIVE-16075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ashutosh Chauhan updated HIVE-16075:
------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to master. Thanks, Yunfei!
> MetaStore needs to reinitialize log4j to allow log specific settings via hiveconf take effect
> ----------------------------------------------------------------------------------------------
>
> Key: HIVE-16075
> URL: https://issues.apache.org/jira/browse/HIVE-16075
> Project: Hive
> Issue Type: Improvement
> Components: Metastore
> Affects Versions: 2.2.0
> Reporter: yunfei liu
> Assignee: yunfei liu
> Priority: Minor
> Fix For: 3.0.0
>
> Attachments: HIVE-16075.1.patch
>
>
> when I start hive metastore with command:
> {quote}
> {{hive --service metastore -hiveconf hive.log.file=hivemetastore.log -hiveconf hive.log.dir=/home/yun/hive/log}}
> {quote}
> The two log parameters won't take effect because after metastore copy hive conf parameters into java system properties, it doesn't reinitialize log4j.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)