[
https://issues.apache.org/jira/browse/OOZIE-2869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977145#comment-15977145
]
Peter Cseh commented on OOZIE-2869:
-----------------------------------
Let me clarify:
1) implement OOZIE-2601 to incorporate local jar support in sharelib
2) by default, create a sharelib named {{mapreduce}} which will contain the MR
jars using local paths as those jars are on every machine
3) users can add mapreduce jars to any action using
{{oozie.action.sharelib.for.ACTION}} just like now. They could add MR jars into
Java, Spark or Shell actions easily.
This way we won't introduce a special way just to handle MR jars for historic
reasons.
> OYA: Introduce <mr-jars /> inside <launcher />
> ----------------------------------------------
>
> Key: OOZIE-2869
> URL: https://issues.apache.org/jira/browse/OOZIE-2869
> Project: Oozie
> Issue Type: Sub-task
> Components: action
> Affects Versions: 5.0.0
> Reporter: Andras Piros
> Fix For: 5.0.0
>
>
> Since Oozie On YARN doesn't fire a map only job to fire all the other
> applications (hence the transition from {{LauncherMapper}} to
> {{LauncherAM}}), no need to bundle the MapReduce JARs within Oozie's default
> sharelib.
> Nevertheless, it's a common, but discouraged use case that MapReduce tasks
> are fired using Java Action. So we need an XSD extension within
> {{workflow.xsd}}:
> * an {{xs:boolean}} valued {{<mr-jars />}} within {{<launcher />}} within
> {{<application />}}
> * defaults to {{false}}
> * its value is used within
> [{{JavaActionExecutor.needToAddMRJars()}}|https://github.com/apache/oozie/blob/oya/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java#L1342]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
