You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "BELUGA BEHR (JIRA)" <ji...@apache.org> on 2018/04/12 13:42:00 UTC
[jira] [Created] (HIVE-19190) Improve Logging for SemanticException
Handling
BELUGA BEHR created HIVE-19190:
----------------------------------
Summary: Improve Logging for SemanticException Handling
Key: HIVE-19190
URL: https://issues.apache.org/jira/browse/HIVE-19190
Project: Hive
Issue Type: Improvement
Components: HiveServer2
Affects Versions: 2.3.2, 3.0.0
Reporter: BELUGA BEHR
Attachments: table_not_found_example.txt
Please improve the logging for queries that fail with SemanticException. For example, when performing an action on a table that does not exist. The most common reason why this happens is that someone fat fingers the table/column name. It is not a system error pe se, but a user validation error. This is not something the cluster administrator should have to worry about. Yet, Hive performs some pretty extreme logging on the matter. I have attached to this JIRA the logging produced by a single submission of the following query:
{code:sql}
select * from madeup';
{code}
For SemanticException exceptions, please print the Exception {{getMessage()}} to the server INFO logging so that the query's life-cycle can be traced, but do not blast ERRORs and stack traces to the log file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)