hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naveen Gangam (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-19302) Logging Too Verbose For TableNotFound
Date Thu, 27 Sep 2018 19:48:00 GMT

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

Naveen Gangam updated HIVE-19302:
---------------------------------
       Resolution: Fixed
    Fix Version/s: 4.0.0
           Status: Resolved  (was: Patch Available)

Fix has been pushed to master. Thank you for your contribution [~afan]. Closing the jira.

> 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
>            Assignee: Alice Fan
>            Priority: Minor
>             Fix For: 4.0.0
>
>         Attachments: HIVE-19302.4.patch, HIVE-19302.5.patch, HIVE-19302.6.patch, HIVE-19302.7.patch,
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)

Mime
View raw message