[
https://issues.apache.org/jira/browse/HADOOP-5348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677328#action_12677328
]
Steve Loughran commented on HADOOP-5348:
----------------------------------------
Proposed features
-something to take an exception and turn it (and any nested exceptions) into
the wire format
-have a constructor that doesn't generate a stack trace, for lower cost
construction of the exceptions
-retain things like classname and stack trace when creating the wire format
-ability for the far end to decode the exception into a class that clients
with hadoop-core.jar will be guaranteed to have
-Utility code to push out into a human readable form in web interface
-possibly: a way to add a stable fault-code string that could be used for
client side tests that was not as brittle as searching for text strings
Non-goals
-seamless conversion back into a throwable chain on the client side. We are not
trying to do RMI here
-all the complexity of SOAP1.2 faults with actors, chained subfault-codes, etc.
. We are not trying to do SOAP or JAX-WS here
> Create a stable wire format for exceptions
> ------------------------------------------
>
> Key: HADOOP-5348
> URL: https://issues.apache.org/jira/browse/HADOOP-5348
> Project: Hadoop Core
> Issue Type: New Feature
> Components: ipc
> Affects Versions: 0.20.0, 0.21.0
> Reporter: Steve Loughran
>
> 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.
