[OOZIE-2686] OYA: Find places where to add MR specific classes/configs instead of handling them in JavaActionExecutor

• Type: Sub-task
• Status: Resolved
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: 5.0.0
• Assignee: Peter Bacsko
• Reporter: Gézapeti
• Created: 26/Sep/16 11:52
• Updated: 20/Sep/17 12:56
• Resolved: 20/Sep/17 12:56

Description

While work is in progress on OYA, we've introduced some MR specific things in JavaActionExecutor, which are probably not needed for every action.
Find the appropriate place for these:

• remove from JavaActionExecutor.createBaseHadoopConf:

          // FIXME - think about this!
          Element e = actionXml.getChild("config-class", ns);
          if (e != null) {
              conf.set(LauncherMapper.OOZIE_ACTION_CONFIG_CLASS, e.getTextTrim());
          }
  

• MR jars are added in JavaActionExecutor.createAppSubmissionContext

          ClasspathUtils.addMapReduceToClasspath(env, launcherJobConf);
  

• logging setup in JavaActionExecutor.createAppSubmissionContext and in LauncherAM has to be worked on.

Issue Links

• duplicates: OOZIE-2869 Ability to add/remove MapReduce jars from action classpath.