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 "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/03/09 22:55:38 UTC

[jira] [Updated] (MAPREDUCE-3523) Exclude mrapp-generated-classpath from published jars

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

Allen Wittenauer updated MAPREDUCE-3523:
----------------------------------------
    Fix Version/s:     (was: 0.24.0)

> Exclude mrapp-generated-classpath from published jars
> -----------------------------------------------------
>
>                 Key: MAPREDUCE-3523
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3523
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Hitesh Shah
>
> Downstream projects will be generating their own classpath file to allow yarn to launch containers correctly in a unit-test env which may potentially create a clash if 2 versions are present. 
> The current code in MRApps assumes that the generated classpath is always present which may need to be addressed if this file is not present when deployed on a cluster. An option for a fix could be to pass the location of the classpath file via the MiniYarnCluster constructor and propagate that to MRApps via some form of configuration value.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)