You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2014/04/11 20:38:20 UTC

[jira] [Updated] (YARN-1931) Private API change in YARN-1824 in 2.4 broke compatibility with previous releases

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

Vinod Kumar Vavilapalli updated YARN-1931:
------------------------------------------

    Priority: Major  (was: Blocker)
    Assignee: Sandy Ryza
     Summary: Private API change in YARN-1824 in 2.4 broke compatibility with previous releases  (was: YARN-1824 in 2.4 broke compatibility with previous releases)

I'm okay with this for now. But I'm requesting YARN app frameworks like TEZ, Spark and Twill to do a scan of their projects and get rid of YARN private APIs that are in use.

Assigning to Sandy. Reducing priority and fixing title.

> Private API change in YARN-1824 in 2.4 broke compatibility with previous releases
> ---------------------------------------------------------------------------------
>
>                 Key: YARN-1931
>                 URL: https://issues.apache.org/jira/browse/YARN-1931
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: applications
>    Affects Versions: 2.4.0
>            Reporter: Thomas Graves
>            Assignee: Sandy Ryza
>         Attachments: YARN-1931-1.patch, YARN-1931.patch
>
>
> YARN-1824 broke compatibility with previous 2.x releases by changes the API's in org.apache.hadoop.yarn.util.Apps.{setEnvFromInputString,addToEnvironment}  The old api should be added back in.
> This affects any ApplicationMasters who were using this api.  It also breaks previously built MapReduce libraries from working with the new Yarn release as MR uses this api. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)