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 "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2014/01/15 01:25:19 UTC
[jira] [Updated] (YARN-1601) 3rd party JARs are missing from
hadoop-dist output
[ https://issues.apache.org/jira/browse/YARN-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alejandro Abdelnur updated YARN-1601:
-------------------------------------
Attachment: YARN-1601.patch
Patch that adds to the hadoop-yarn POM the submodules as dependencies, this is required to be able to populate the /share/hadoop/lib/ dir with 3rd party JARs used by Yarn. The hadoop-yarn POM isn't a parent of any other POM so this does not affect existing dependencies. It just makes the assembly for yarn to pick up Yarn 3rd party JARs when creating the tarball
> 3rd party JARs are missing from hadoop-dist output
> --------------------------------------------------
>
> Key: YARN-1601
> URL: https://issues.apache.org/jira/browse/YARN-1601
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 3.0.0, 2.4.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Attachments: YARN-1601.patch
>
>
> With the build changes of YARN-888 we are leaving out all 3rd party JArs used directly by YARN under /share/hadoop/yarn/lib/.
> We did not notice this when running minicluster because they all happen to be in the classpath from hadoop-common and hadoop-yarn.
> As 3d party JARs are not 'public' interfaces we cannot rely on them being provided to yarn by common and hdfs. (ie if common and hdfs stop using a 3rd party dependency that yarn uses this would break yarn if yarn does not pull that dependency explicitly).
> Also, this will break bigtop hadoop build when they move to use branch-2 as they expect to find jars in /share/hadoop/yarn/lib/
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)