You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Hari Sankar Sivarama Subramaniyan (JIRA)" <ji...@apache.org> on 2015/12/15 02:59:46 UTC
[jira] [Updated] (HIVE-12675) PerfLogger should log performance
metrics at debug level
[ https://issues.apache.org/jira/browse/HIVE-12675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hari Sankar Sivarama Subramaniyan updated HIVE-12675:
-----------------------------------------------------
Description: 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. (was: As more and more subcomponents are 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.)
> 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
>
> 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)