[
https://issues.apache.org/jira/browse/HIVE-12949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135634#comment-15135634
]
Hari Sankar Sivarama Subramaniyan commented on HIVE-12949:
----------------------------------------------------------
[~mohitsabharwal] Thanks for the comments. If you see, LogDivertAppender has a
Filter which decides which server side message to be logged at the session
based on the logging level. The logic is here :
https://github.com/apache/hive/blob/master/service/src/java/org/apache/hive/service/cli/operation/LogDivertAppender.java#L150.
As for the operation log, it depends on the parentSession's HiveConf which
decides the logging level as initiated here :
https://github.com/apache/hive/blob/master/service/src/java/org/apache/hive/service/cli/operation/Operation.java#L246
Everytime you modify the parameter from the session, the HiveConf object
corresponding to the session gets modified to reflect the parameter change and
hence the operation is initialized with this information.
I tested this parameter with the current master and the feature works as
intended, if you feel that this is not the case, please update the jira/title
to include the actual issue with a testcase. I don't think a description change
of hive.server2.logging.operation.level is the correct way to fix this problem
if this is an actual bug.
Thanks
Hari
> 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)
