[
https://issues.apache.org/jira/browse/HIVE-10775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Cowie updated HIVE-10775:
--------------------------------
Attachment: HIVE-10775.1.patch
Just the beginning, of course; there are hundreds of calls to
printStackTrace(). Thought I should get some feedback now, however, to see if
I'm on the right track. Code Review if someone cares to offer one?
(I'm working through them roughly in the order we seem to be hitting them as
our code calls them from other libraries)
AfC
> Frequent calls to printStackTrace() obscuring legitimate problems
> -----------------------------------------------------------------
>
> Key: HIVE-10775
> URL: https://issues.apache.org/jira/browse/HIVE-10775
> Project: Hive
> Issue Type: Test
> 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
(v6.3.4#6332)
