[
https://issues.apache.org/jira/browse/OOZIE-2869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Cseh updated OOZIE-2869:
------------------------------
Attachment: OOZIE-2869.001.patch
As a first step I've defined a property to provide the possibility to
add/remove jars from the classpath for each action type using the
"oozie.action.mapreduce.needed.for" prefix.
> OYA: Introduce default mapreduce sharelib
> -----------------------------------------
>
> 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
> Assignee: Peter Cseh
> Fix For: 5.0.0b1
>
> Attachments: OOZIE-2869.001.patch
>
>
> 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 some default {{mapreduce}} sharelib
> that can be used by customers after OOZIE-2601 will have been implemented:
> # by default, create a sharelib named {{mapreduce}} which will contain the MR
> jars using local paths as those jars are on every machine
> # 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 message was sent by Atlassian JIRA
(v6.4.14#64029)
