hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergio Peña (JIRA) <j...@apache.org>
Subject [jira] [Commented] (HIVE-14370) printStackTrace() called in Operator.close()
Date Thu, 28 Jul 2016 15:48:20 GMT

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

Sergio Peña commented on HIVE-14370:
------------------------------------

+1

You should use the '.patch' extension instead of '.diff'.
Also, click on submit patch so that HiveQA grabs the file and run the tests.

> printStackTrace() called in Operator.close()
> --------------------------------------------
>
>                 Key: HIVE-14370
>                 URL: https://issues.apache.org/jira/browse/HIVE-14370
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: David Karoly
>            Assignee: David Karoly
>            Priority: Minor
>         Attachments: HIVE-14370.1.diff
>
>
> Operator.close() calls printStackTrace() if something goes wrong, making the stack trace
go to stderr instead of logs and losing the timestamp. We should use LOG.warn instead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message