[ 
https://issues.apache.org/jira/browse/HIVE-12949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127357#comment-15127357
 ] 

Hari Sankar Sivarama Subramaniyan commented on HIVE-12949:
----------------------------------------------------------

Hi [~mohitsabharwal],  Is hive.server2.logging.operation.level not settable 
from a HS2 session?  Have you tried it with a HS2 JDBC client such as beeline 
by doing "set  hive.server2.logging.operation.level=VERBOSE", run a Hive query 
with MR tasks, "set  hive.server2.logging.operation.level= EXECUTION", run the 
same query etc and see a logging behavior change. You can further test it by 
opening multiple sessions to the same server and see if the above mentioned 
behavior is taking place for each independent session. If this is not the case, 
then this issue requires more attention than a description change. Rather, its 
a bug because it defeats the purpose of the original jira HIVE-10119. 
The hiveserver2 level parameter is hive.server2.logging.operation.enabled which 
is to enable/disable any client side logging.

Also, can you please clarify what "currently" refers to in the jira description.

Can you please clarify the above questions before we change the description of 
the mentioned parameter.

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)

Reply via email to