[
https://issues.apache.org/jira/browse/HIVE-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16977656#comment-16977656
]
Piyush Patel commented on HIVE-5208:
------------------------------------
[~leftyl] Although this seems possible solution, having straight forward
solution for developers could be appreciated. In second option, it is upto
Sysadmins to configure logging on Hive server2. In the first case, I get
HiveServer2 Kerberos principal or keytab is not correctly configured. I am
actually not sure if we can pass principal and keytab as parameters to
Hiveserver2 cli.
> 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)
