[
https://issues.apache.org/jira/browse/YARN-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13707362#comment-13707362
]
Sandy Ryza commented on YARN-912:
---------------------------------
bq. Sandy, what do you mean by client.api? Which client?
My bad. I thought these were only relevant for AMRMClient. But my main point
was that there's not much precedent and it's not very useful to package classes
by what kind of class they are. I would say we should put them into
org.apache.hadoop.yarn.
I'm now noticing that YarnException and YarnRuntimeException are in the
org.apache.hadoop.yarn.exceptions package as well, so if it's too late to
change that, I'm fine with putting these in the exceptions package as well.
> Create exceptions package in common/api for yarn and move client facing
> exceptions to them
> ------------------------------------------------------------------------------------------
>
> Key: YARN-912
> URL: https://issues.apache.org/jira/browse/YARN-912
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.1.0-beta
> Reporter: Bikas Saha
> Assignee: Mayank Bansal
> Attachments: YARN-912-trunk-1.patch, YARN-912-trunk-2.patch
>
>
> Exceptions like InvalidResourceBlacklistRequestException,
> InvalidResourceRequestException, InvalidApplicationMasterRequestException etc
> are currently inside ResourceManager and not visible to clients.
--
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
