[
https://issues.apache.org/jira/browse/HIVE-12675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058825#comment-15058825
]
Hari Sankar Sivarama Subramaniyan commented on HIVE-12675:
----------------------------------------------------------
[~sershe] It would be possible to do the following from the user side if he/she
needs the performance metrics :
{code}
log4j.logger.org.apache.hadoop.hive.ql.log.PerfLogger=DEBUG
{code}
This way you can make sure that we get DEBUG level logs only for PerfLogger and
INFO level logs for others (assuming that hive.root.logger=INFO). I will update
the documentation in
https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties and
https://cwiki.apache.org/confluence/display/Hive/GettingStarted#GettingStarted-HiveLogging
so that the user is aware of this.
Thanks
Hari
> PerfLogger should log performance metrics at debug level
> --------------------------------------------------------
>
> Key: HIVE-12675
> URL: https://issues.apache.org/jira/browse/HIVE-12675
> Project: Hive
> Issue Type: Bug
> Reporter: Hari Sankar Sivarama Subramaniyan
> Assignee: Hari Sankar Sivarama Subramaniyan
> Attachments: HIVE-12675.1.patch
>
>
> As more and more subcomponents of Hive (Tez, Optimizer) etc are using
> PerfLogger to track the performance metrics, it will be more meaningful to
> set the PerfLogger logging level to DEBUG. Otherwise, we will print the
> performance metrics unnecessarily for each and every query if the underlying
> subcomponent does not control the PerfLogging via a parameter on its own.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)