[jira] [Commented] (OOZIE-2074) Compatibility issue with Yarn and Hadoop 0.23/2.x

2014-11-25 Thread Shwetha G S (JIRA) 

[ 
https://issues.apache.org/jira/browse/OOZIE-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14224322#comment-14224322
 ] 

Shwetha G S commented on OOZIE-2074:


+1

 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)

[jira] [Commented] (OOZIE-2074) Compatibility issue with Yarn and Hadoop 0.23/2.x

2014-11-25 Thread Shwetha G S (JIRA) 

[ 
https://issues.apache.org/jira/browse/OOZIE-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)

[jira] [Commented] (OOZIE-2074) Compatibility issue with Yarn and Hadoop 0.23/2.x

2014-11-25 Thread Shwetha G S (JIRA) 

[ 
https://issues.apache.org/jira/browse/OOZIE-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14224350#comment-14224350
 ] 

Shwetha G S commented on OOZIE-2074:


Never mind, class check might not work. Committed to trunk. Thanks JD

 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)

[jira] [Commented] (OOZIE-2074) Compatibility issue with Yarn and Hadoop 0.23/2.x

2014-11-24 Thread Jaydeep Vishwakarma (JIRA) 

[ 
https://issues.apache.org/jira/browse/OOZIE-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14222941#comment-14222941
 ] 

Jaydeep Vishwakarma commented on OOZIE-2074:


Checking the yarn.resourcemanager.webapp.address property will be fine 
instead of yarn.resourcemanager.address.

 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

 We are using yarn.resourcemanager.address for checking the hadoop version 
 in jobUtils. Here is the code snippet. 
  // Hadoop 0.20/1.x.
   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);
   }
 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)

[jira] [Commented] (OOZIE-2074) Compatibility issue with Yarn and Hadoop 0.23/2.x

2014-11-24 Thread Hadoop QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/OOZIE-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14223018#comment-14223018
 ] 

Hadoop QA commented on OOZIE-2074:
--

Testing JIRA OOZIE-2074

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 1557
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/2106/

 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)