[
https://issues.apache.org/jira/browse/MAPREDUCE-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Seth updated MAPREDUCE-4067:
--------------------------------------
Attachment: MR4067.txt
Turns out the RPC/Security layers don't handle anything other than IOException
very well (ugi.doAs will result in UndeclaredThrowableException if not an
IOException).
Changes in the patch
- All APIs also throw IOException (for exception originating in the RPC layer)
- YarnRemoteException (continues to extend IOE) can be extended for custom
exceptions.
- The old YarnRemoteExceptionPBImpl moved as a record to SerializedException
(used by some yarn APIs)
- Added some custom exceptions like UnknownAppId
If folks are ok with this patch, would like to rename YarnRemoteException to
YarnException, and the existing YarnException to YarnRuntimeException before
this is checked in.
> Replace YarnRemoteException with IOException in MRv2 APIs
> ---------------------------------------------------------
>
> Key: MAPREDUCE-4067
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4067
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Jitendra Nath Pandey
> Assignee: Siddharth Seth
> Priority: Blocker
> Attachments: MR4067.txt
>
>
> YarnRemoteException is defined as a generic wrapper for all the exceptions in
> yarn. I think we should instead throw IOExceptions in the API, which can
> later be extended for more specialized exceptions without breaking
> compatibility.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
