Details
-
Sub-task
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
2.2.0, 3.0.0
-
None
Description
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.
Attachments
Attachments
Issue Links
- is duplicated by
-
HIVE-19190 Improve Logging for SemanticException Handling
- Resolved