hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanth Jayachandran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-15314) ThriftCLIService should LOG.error rather than LOG.warn when Exception occurs
Date Wed, 30 Nov 2016 08:58:59 GMT

    [ https://issues.apache.org/jira/browse/HIVE-15314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707991#comment-15707991
] 

Prasanth Jayachandran commented on HIVE-15314:
----------------------------------------------

I guess the intention here is to log and set error status in thrift response. If my understanding
is correct, these exceptions are logged just for debugging purpose and are usually handled/acted
upon by the clients. In case of error response, the client will throw HiveException that will
contain the stacktrace received from ThriftCLIService. 

[~thejas] I guess that was your initial intention, right?

> 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)

Mime
View raw message