You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Lefty Leverenz (JIRA)" <ji...@apache.org> on 2015/06/03 02:50:50 UTC

[jira] [Updated] (HIVE-10119) Allow Log verbosity to be set in hiveserver2 session

     [ https://issues.apache.org/jira/browse/HIVE-10119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lefty Leverenz updated HIVE-10119:
----------------------------------
    Labels:   (was: TODOC1.2)

> Allow Log verbosity to be set in hiveserver2 session
> ----------------------------------------------------
>
>                 Key: HIVE-10119
>                 URL: https://issues.apache.org/jira/browse/HIVE-10119
>             Project: Hive
>          Issue Type: Improvement
>          Components: HiveServer2
>            Reporter: Hari Sankar Sivarama Subramaniyan
>            Assignee: Hari Sankar Sivarama Subramaniyan
>             Fix For: 1.2.0
>
>         Attachments: HIVE-10119.1.patch, HIVE-10119.2.patch, HIVE-10119.3.patch, HIVE-10119.4.patch
>
>
> We need to be able to set logging per HS2 session.
> The client often uses the map-reduce completion matrix (Execution) that shows up in Beeline to debug performance. User might not want the verbose log view all the time since it obfuscates the Execution information. Hence the client should be able to change the verbosity level.
> Also, there are 2 levels of verbosity at HS2 logging and not 3. The users might want Execution + Performance counters only - so that level needs to be added.
> So for logs,  the user should be able to set 3 levels of verbosity in the session, that will override the default verbosity specified in the hive-site.xml file.
> 0. None - IGNORE
> 1. Execution - Just shows the map-reduce tasks completing 
> 2. Performance - Execution + Performance counters dumped at the end
> 3. Verbose - All logs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)