[
https://issues.apache.org/jira/browse/OOZIE-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856806#comment-15856806
]
Robert Kanter commented on OOZIE-1770:
--------------------------------------
For {{launcher.lib}}, I think that's supposed to refer to this property in
oozie-site
{code:xml}
<property>
<name>oozie.action.ship.launcher.jar</name>
<value>false</value>
<description>
Specifies whether launcher jar is shipped or not.
</description>
</property>
{code}
which makes Oozie generate a jar containing the Oozie-supplied code that
otherwise would be in the sharelib. This is useful for users who build their
own sharelib instead of using the Oozie-provided one. For instance, if you
provided your own Pig jars instead of using the Pig sharelib, you would be
missing Oozie classes like {{PigMain}} and {{LauncherMapper}}. Setting this
property to {{true}} would have Oozie provide those for you in that case. So
you can use any workflow, no need for a special one. The easiest way to verify
this is probably to go and remove the {{oozie-*}} jars from a Sharelib (e.g.
Pig sharelib), turn on this property, and see if the (Pig) action still works.
For Oozie on MapReduce, the equivalent of launcher.xml is the Launcher Job's
jobconf XML file, which is available in the JHS and elsewhere. With OYA,
that's been replaced with this launcher.xml file, which I don't think we're
currently exposing anywhere. Being able to get the contents of that file would
likely be useful for debugging. A place to make this data available could be
the launcher AM output. It might be better to wait to add this until we do
OOZIE-2702 and make it DEBUG or TRACE level to reduce spam. Another option is
that it might be possible to include the launcher.xml file with the aggregated
logs; IIRC, the NM will blindly process any files from that dir.
> Create Oozie Application Master for YARN
> ----------------------------------------
>
> Key: OOZIE-1770
> URL: https://issues.apache.org/jira/browse/OOZIE-1770
> Project: Oozie
> Issue Type: New Feature
> Reporter: Bowen Zhang
> Assignee: Peter Cseh
> Attachments: OOZIE-1770-001.patch, OOZIE-1770-002.patch,
> OOZIE-1770-003.patch, OOZIE-1770-004.patch, OOZIE-1770-005.patch,
> OOZIE-1770-006.patch, OOZIE-1770-007.patch, OOZIE-1770-008.patch,
> OOZIE-1770-009.patch, OozieYarnAM.pdf, oya.patch, oya-rm-screenshot.jpg, OYA
> Scoping Doc 001.pdf, Prelim OYA Scoping Doc 001.pdf, Prelim OYA Scoping Doc
> 002.pdf, Prelim OYA Scoping Doc 003.pdf
>
>
> After the first release of oozie on hadoop 2, it will be good if users can
> set execution engine in oozie conf, be it YARN AM or traditional MR. We can
> target this for post oozie 4.1 release.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
