[
https://issues.apache.org/jira/browse/PIG-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564097#action_12564097
]
Benjamin Reed commented on PIG-80:
----------------------------------
Alright! Someone else is using 1.6! Unfortunately, I got nixed on requiring
1.6, so this needs to use initCause(Throwable) rather than using the
constructor.
If I may, I'd like to expand this bug to cover all instances of new
XXXException(e.getMessage()) or e.fillStackTrace(), there have been cases where
having the root cause would have GREATLY!!! reduced the debug time. At the same
time we should also remove all e.printStackTrace() calls.
> Stacktrace information is lost at MapReduceLauncher.java:289
> ------------------------------------------------------------
>
> Key: PIG-80
> URL: https://issues.apache.org/jira/browse/PIG-80
> Project: Pig
> Issue Type: Bug
> Components: impl
> Affects Versions: 0.1.0
> Reporter: Benjamin Francisoud
> Priority: Minor
> Attachments: PIG-80-v01.patch
>
>
> {code:java}
> ...
> }catch (Exception e) {
> // Do we need different handling for different exceptions
> e.printStackTrace();
> throw new IOException(e.getMessage());
> }finally{ ...
> {code}
> in my case the sandard output is redirtected to /dev/null so
> "e.printStackTrace();" is lost.
> it should be :
> {code:java}throw new IOException(e);{code}
> no getMessage() because we loose the rest of the stacktrace
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
