You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Mohit Sabharwal (JIRA)" <ji...@apache.org> on 2016/02/01 22:21:40 UTC
[jira] [Commented] (HIVE-12949) Fix description of
hive.server2.logging.operation.level
[ https://issues.apache.org/jira/browse/HIVE-12949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127059#comment-15127059 ]
Mohit Sabharwal commented on HIVE-12949:
----------------------------------------
[~hsubramaniyan], could you take a quick look? thanks.
> Fix description of hive.server2.logging.operation.level
> -------------------------------------------------------
>
> Key: HIVE-12949
> URL: https://issues.apache.org/jira/browse/HIVE-12949
> Project: Hive
> Issue Type: Bug
> Components: Configuration
> Reporter: Mohit Sabharwal
> Assignee: Mohit Sabharwal
> Attachments: HIVE-12949.patch
>
>
> Description of {{hive.server2.logging.operation.level}} states that this property is available to set at session level. This is not correct. The property is only settable at HS2 level currently.
> A log4j appender is created just once currently - based on logging level specified by this config, at OperationManager init time in initOperationLogCapture(). And there is only one instance of OperationManager.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)