[ https://issues.apache.org/jira/browse/HIVE-15314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15708041#comment-15708041 ]
Fei Hui commented on HIVE-15314: -------------------------------- when queries failed, i checked the log /tmp/hadoop/hive.log and found that 2016-11-30T11:52:49,401 WARN [909b45b3-deed-4a39-a54d-864e97b057b3909b45b3-deed-4a39-a54d-864e97b057b3b6b20a18-cef5-4b3b-ae09-65ab5f8c880eb6b20a18-cef5-4b3b-ae09-65ab5f8c880ec671ec17-c7a4-4811-a9f8-68bb4bbcb9a5c671ec17-c7a4-4811-a9f8-68bb4bbcb9a555adbcc6-c1fa-4646-9c83-92a1f3c21b4155adbcc6-c1fa-4646-9c83-92a1f3c21b41HiveServer2-Handler-Pool: Thread-42]: thrift.ThriftCLIService (ThriftCLIService.java:ExecuteStatement(515)) - Error executing statement: Here is 'WARN', but messages contains 'Error executing statement'. So i'm confused. If it's 'ERROR',maybe i understand it's serious error That's point thanks [~prasanth_j]'s reply > ThriftCLIService should LOG.error rather than LOG.warn when Exception occurs > ---------------------------------------------------------------------------- > > Key: HIVE-15314 > URL: https://issues.apache.org/jira/browse/HIVE-15314 > Project: Hive > Issue Type: Bug > Components: CLI, Logging > Affects Versions: 2.2.0 > Reporter: Fei Hui > Assignee: Fei Hui > Attachments: HIVE-15314.1.patch > > > When catch exception, critical error occurs, > and the message in log is ''Error executing statement", "Error getting type > info", etc. > So we should use LOG.error, and it will remind users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)