[
https://issues.apache.org/jira/browse/OOZIE-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14224332#comment-14224332
]
Shwetha G S commented on OOZIE-2074:
------------------------------------
Actually, instead of checking if a config has been set(which can be set because
of other reasons for example migration etc), we should check if a 2.0 specific
class is in classpath. Wouldn't that work better?
> Compatibility issue with Yarn and Hadoop 0.23/2.x
> -------------------------------------------------
>
> Key: OOZIE-2074
> URL: https://issues.apache.org/jira/browse/OOZIE-2074
> Project: Oozie
> Issue Type: Bug
> Reporter: Jaydeep Vishwakarma
> Assignee: Jaydeep Vishwakarma
> Attachments: OOZIE-2074-v0.patch
>
>
> We are using "yarn.resourcemanager.address" for checking the hadoop version
> in jobUtils. Here is the code snippet.
> // Hadoop 0.20/1.x.
> {code}
> if (defaultConf.get("yarn.resourcemanager.address") == null) {
> // Duplicate hadoop 1.x code to workaround MAPREDUCE-2361 in Hadoop
> 0.20
> // Refer OOZIE-1806.
> String filepath = file.toUri().getPath();
> String classpath = conf.get("mapred.job.classpath.files");
> conf.set("mapred.job.classpath.files", classpath == null
> ? filepath
> : classpath + System.getProperty("path.separator") + filepath);
> URI uri = fs.makeQualified(file).toUri();
> DistributedCache.addCacheFile(uri, conf);
> }
> else { // Hadoop 0.23/2.x
> DistributedCache.addFileToClassPath(file, conf, fs);
> }
> {code}
> But this is being used in JavaActionExecutor to set jobTracker.
> conf.set(HADOOP_YARN_RM, jobTracker);
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
