BELUGA BEHR created HIVE-19190:

             Summary: Improve Logging for SemanticException Handling
                 Key: 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:

select * from madeup';
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

Reply via email to