You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2012/07/07 15:00:35 UTC

[jira] [Updated] (MAPREDUCE-4067) Replace YarnRemoteException with IOException in MRv2 APIs

     [ https://issues.apache.org/jira/browse/MAPREDUCE-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Harsh J updated MAPREDUCE-4067:
-------------------------------

            Priority: Critical  (was: Blocker)
    Target Version/s: 2.0.1-alpha  (was: 2.0.0-alpha)

(Don't think this is a blocker, but reset if I'm wrong. An explanation of why its a blocker would be good too, thanks! :))
                
> Replace YarnRemoteException with IOException in MRv2 APIs
> ---------------------------------------------------------
>
>                 Key: MAPREDUCE-4067
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4067
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Jitendra Nath Pandey
>            Assignee: Siddharth Seth
>            Priority: Critical
>         Attachments: MR4067.txt
>
>
> YarnRemoteException is defined as a generic wrapper for all the exceptions in yarn. I think we should instead throw IOExceptions in the API, which can later be extended for more specialized exceptions without breaking compatibility.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira