hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-142) Change YARN APIs to throw IOException
Date Thu, 07 Feb 2013 14:11:13 GMT

    [ https://issues.apache.org/jira/browse/YARN-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573516#comment-13573516

Tom White commented on YARN-142:

> I think it'd be useful to have the APIs throw IOException and YarnRemoteException. The
IOException indicating errors from the RPC layer, YarnException indicating errors from Yarn

I see the latest patch has

{noformat}throws UnknownApplicationException,YarnRemoteException,IOException{noformat}

even though UnknownApplicationException is a subclass of YarnRemoteException, and YarnRemoteException
is a subclass of IOException. It would be simpler to make the method signature

{noformat}throws IOException{noformat}

and draw attention to the different subclasses in the javadoc if needed.
> Change YARN APIs to throw IOException
> -------------------------------------
>                 Key: YARN-142
>                 URL: https://issues.apache.org/jira/browse/YARN-142
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>    Affects Versions: 0.23.3, 2.0.0-alpha
>            Reporter: Siddharth Seth
>            Assignee: Xuan Gong
>            Priority: Critical
>         Attachments: YARN-142.1.patch, YARN-142.2.patch, YARN-142.3.patch, YARN-142.4.patch
> Ref: MAPREDUCE-4067
> All YARN APIs currently throw YarnRemoteException.
> 1) This cannot be extended in it's current form.
> 2) The RPC layer can throw IOExceptions. These end up showing up as UndeclaredThrowableExceptions.

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

View raw message