[ https://issues.apache.org/jira/browse/HIVE-24189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17200697#comment-17200697 ]
Zoltan Haindrich commented on HIVE-24189: ----------------------------------------- I think we already log the statement a few places - so I don't really see the need to create a conf key to toggle this one I know we might have some confusion in our contribution guide - earlier approach was to attach patches to the jira... a few months ago we've moved testing/etc to github - so could you open a PR with your changes? > Enable logging executed raw sql statements for HiveServer2 before parsing > -------------------------------------------------------------------------- > > Key: HIVE-24189 > URL: https://issues.apache.org/jira/browse/HIVE-24189 > Project: Hive > Issue Type: Improvement > Components: HiveServer2 > Affects Versions: 3.1.0 > Reporter: ji.chen > Assignee: ji.chen > Priority: Trivial > Attachments: > 0001-Enable-logging-executed-sql-statements-for-HiveServe.patch > > > Current Hiveserver2 lacks the feature of logging command related statement in > hiveserver2 log files. It will cause inconvenience for customer to debug > command related statement. > We have follow case: > HiveServer2 is crashed when our customer executed SET statement, however we > can't find exact SET statement customer was executed before.If raw statement > is recorded in hiveserver2 logs, it will facilitate us to debugging command > related statement issue. > So we propose a improvement to write the raw statement in hiveserver2 log > property hive.session.raw.statement.verbose is introduced to control output > of raw sql statement, by default, it is enabled. > it can be disabled by setting hive.session.raw.statement.verbose to false. > > > We have attached patch -- This message was sent by Atlassian Jira (v8.3.4#803005)