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

["Peter Cseh (JIRA)" <ji...@apache.org>]

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

Peter Cseh resolved OOZIE-2686.
-------------------------------
    Resolution: Duplicate

> OYA: Find places where to add MR specific classes/configs instead of handling them in JavaActionExecutor
> --------------------------------------------------------------------------------------------------------
>
>                 Key: OOZIE-2686
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2686
>             Project: Oozie
>          Issue Type: Sub-task
>    Affects Versions: 5.0.0
>            Reporter: Peter Cseh
>            Assignee: Peter Bacsko
>            Priority: Critical
>
> 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: 
> {code}
>         // FIXME - think about this!
>         Element e = actionXml.getChild("config-class", ns);
>         if (e != null) {
>             conf.set(LauncherMapper.OOZIE_ACTION_CONFIG_CLASS, e.getTextTrim());
>         }
> {code}
> * MR jars are added in JavaActionExecutor.createAppSubmissionContext 
> {code}
>         ClasspathUtils.addMapReduceToClasspath(env, launcherJobConf);
> {code}
> * logging setup in JavaActionExecutor.createAppSubmissionContext  and in LauncherAM has to be worked on.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)