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

Lefty Leverenz commented on HIVE-5208:
--------------------------------------

[~piyushpatel2005], is this what you tried?
 * {{bin/hiveserver2 --hiveconf hive.root.logger=DEBUG,console}}

What about setting hive.server2.logging.operation.level to VERBOSE?

The wiki discusses logging here:
 * [Getting Started - Hive 
Logging|https://cwiki.apache.org/confluence/display/Hive/GettingStarted#GettingStarted-HiveLoggingErrorLogsHiveLogs]
 * [HiveServer2 
Logging|https://cwiki.apache.org/confluence/display/Hive/HiveServer2+Clients#HiveServer2Clients-HiveServer2Logging]

Perhaps the documentation needs to be updated.

> Provide an easier way to capture DEBUG logging
> ----------------------------------------------
>
>                 Key: HIVE-5208
>                 URL: https://issues.apache.org/jira/browse/HIVE-5208
>             Project: Hive
>          Issue Type: Improvement
>          Components: CLI
>    Affects Versions: 0.11.0
>            Reporter: Harsh J
>            Priority: Minor
>
> Capturing debug logging for troubleshooting is painful in Hive today:
> 1. It doesn't log anywhere by default.
> 2. We need to add a long "-hiveconf hive.root.logger=DEBUG,console" to the 
> Hive CLI just to enable the debug flag, or set an equivalent env-var 
> appropriately.
> I suggest we make this simpler via either one of the below:
> 1. Provide a wrapped binary, "hive-debug", so folks can simply re-run
> the "hive-debug" command and re-run their query and capture an output. This 
> could also write to a pre-designated $PWD file.
> 2. Provide a simpler switch, such as "-verbose" that automatically
> toggles the flag instead, much like what Beeline does today already.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to