You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "David Mollitor (Jira)" <ji...@apache.org> on 2020/04/02 03:37:00 UTC

[jira] [Resolved] (HIVE-10775) Frequent calls to printStackTrace() obscuring legitimate problems

     [ https://issues.apache.org/jira/browse/HIVE-10775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Mollitor resolved HIVE-10775.
-----------------------------------
    Resolution: Duplicate

> Frequent calls to printStackTrace() obscuring legitimate problems
> -----------------------------------------------------------------
>
>                 Key: HIVE-10775
>                 URL: https://issues.apache.org/jira/browse/HIVE-10775
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore, Query Processor
>            Reporter: Andrew Cowie
>            Assignee: Andrew Cowie
>            Priority: Minor
>         Attachments: HIVE-10775.1.patch
>
>
> When running test suites built on top of libraries that build on top of ... that use Hive, the signal to noise ratio with exceptions flying past is appalling. Most of this is down to calls to printStackTrace() embedded in this library. HIVE-7697 showed someone cleaning that up and replacing with logging the exception instead. That seems wise (logging can be redirected by the calling test suite).
> So, if you don't object, I'll hunt down the calls to printStackTrace() and replace them with LOG.warn() instead. I'm about half way through the patch now.
> AfC



--
This message was sent by Atlassian Jira
(v8.3.4#803005)