[
https://issues.apache.org/jira/browse/HIVE-12949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135493#comment-15135493
]
Mohit Sabharwal commented on HIVE-12949:
----------------------------------------
Thanks, [~hsubramaniyan]. I tested this on version 1.2 by setting
{{hive.server2.logging.operation.level}} via beeline and it did not work. I
have not tested it on current master.
As I said in the description, from reading the code, it appears that an
appender based on the log level property is created just once at
OperationManager init time (in initOperationLogCapture). Not each time an
operation is issued or even once for every new session. Effectively, logging
level gets fixed when HS2 first comes up and remains the same . Unless I am
missing something here.
> 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)
