[
https://issues.apache.org/jira/browse/YARN-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660411#comment-13660411
]
Siddharth Seth commented on YARN-628:
-------------------------------------
Good catch on the javadoc. That should be fixed.
bq. The only solution is creating a union (IOException, YarnRemoteException)
Or just using a Throwable with an instance check, but that check seems
unnecessary. One downside to the current approach (other than the ugly code) is
that the trace for the exception includes the call to the unwrap method.
> Fix YarnException unwrapping
> ----------------------------
>
> Key: YARN-628
> URL: https://issues.apache.org/jira/browse/YARN-628
> Project: Hadoop YARN
> Issue Type: Sub-task
> Affects Versions: 2.0.4-alpha
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Fix For: 2.0.5-beta
>
> Attachments: YARN-628.txt, YARN-628.txt, YARN-628.txt, YARN-628.txt.2
>
>
> Unwrapping of YarnRemoteExceptions (currently in YarnRemoteExceptionPBImpl,
> RPCUtil post YARN-625) is broken, and often ends up throwin
> UndeclaredThrowableException. This needs to be fixed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
