[
https://issues.apache.org/jira/browse/YARN-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660118#comment-13660118
]
Siddharth Seth commented on YARN-628:
-------------------------------------
I agree; mentioned that along with the first patch. If not this pattern, there
would be something similar - maybe a check on the exception returned before
throwing. Another possible way would be strange parametrization of the
unwrapAndThrow method.
It is dead code; unwrapAndThrow will always throw an Exception.
Do you have suggestions on how this can be done ?, can be part of a follow up
jira.
> 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
