You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Aihua Xu (JIRA)" <ji...@apache.org> on 2018/04/26 17:45:00 UTC

[jira] [Updated] (HIVE-19302) Logging Too Verbose For TableNotFound

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

Aihua Xu updated HIVE-19302:
----------------------------
    Issue Type: Sub-task  (was: Improvement)
        Parent: HIVE-19318

> Logging Too Verbose For TableNotFound
> -------------------------------------
>
>                 Key: HIVE-19302
>                 URL: https://issues.apache.org/jira/browse/HIVE-19302
>             Project: Hive
>          Issue Type: Sub-task
>          Components: HiveServer2
>    Affects Versions: 2.2.0, 3.0.0
>            Reporter: BELUGA BEHR
>            Priority: Minor
>         Attachments: table_not_found_cdh6.txt
>
>
> There is way too much logging when a user submits a query against a table which does not exist.  In an ad-hoc setting, it is quite normal that a user fat-fingers a table name.  Yet, from the perspective of the Hive administrator, there was perhaps a major issue based on the volume and severity of logging.  Please change the logging to INFO level, and do not present a stack trace, for such a trivial error.
>  
> See the attached file for a sample of what logging a single "table not found" query generates.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)