Siddharth Seth updated YARN-635:

    Attachment: YARN-635.2.txt

Rebased patch.

bq. Doubtful on YarnRemoteException renaming. YarnRemoteException helps me 
understand that the exception was generated on the remote server and is useful 
as a piece of debug information.
Wondering if there's a better way to convey this information - maybe via the 
message string. If any of the client libraries start doing more than they do 
rightnow - they could end up generating the same exception as the remote 
server, in which case a single exception helps. A slightly contrived example - 
validating the resource request sent by the user in the AMRMClient.
> Rename YarnRemoteException to YarnException
> -------------------------------------------
>                 Key: YARN-635
>                 URL: https://issues.apache.org/jira/browse/YARN-635
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Xuan Gong
>            Assignee: Xuan Gong
>         Attachments: YARN-635.2.txt, YARN-635.txt

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

Reply via email to