Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.2.0
-
None
-
None
Description
In many cases, the call to printStackTrace bypasses the logging framework, in other cases, the error stack trace is printed and the exception is re-thrown (log-and-throw is a bad pattern), and then there are some other edge cases.
Remove this call and replace with calls to the logging framework or remove altogether if exception is wrapped and re-thrown.
Attachments
Issue Links
- supercedes
-
HIVE-10775 Frequent calls to printStackTrace() obscuring legitimate problems
- Resolved