[
https://issues.apache.org/jira/browse/HADOOP-5348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800795#action_12800795
]
Steve Loughran commented on HADOOP-5348:
----------------------------------------
# I agree, there's no compelling need yet, but as I'm also using it my
junit-as-MR jobs test runner, I've teased it out
# And it's in its own Git branch on github:
[HADOOP-5348-ThrowableWritable|http://github.com/steveloughran/hadoop-common/tree/HADOOP-5348-ThrowableWritable]
# Marked as final as when you are trying to diagnose why things failed, it's
not useful to get an exception that you can't deserialize. Seen that too often
in RMI-land to want to enjoy.
# I'll look at the equals(), copy(), clone(); they are probably mostly IDE
generated.
> Create a ThrowableWritable for serializing exceptions robustly
> --------------------------------------------------------------
>
> Key: HADOOP-5348
> URL: https://issues.apache.org/jira/browse/HADOOP-5348
> Project: Hadoop Common
> Issue Type: New Feature
> Components: ipc
> Affects Versions: 0.21.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Fix For: 0.21.0
>
> Attachments: HADOOP-5348-2.patch, hadoop-5348.patch,
> ThrowableWritable.java
>
>
> HADOOP-5201 and other issues would benefit from a stable representation of
> exceptions, one that can be sent over the network, maybe pushed out to web
> UIs and which we can be 100% sure that the far end will be able to handle if
> they have the hadoop-core JAR on their classpath.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
