[
https://issues.apache.org/jira/browse/OOZIE-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383165#comment-15383165
]
Robert Kanter commented on OOZIE-1770:
--------------------------------------
Now that we won't have Hadoop 1 (i.e. no JobTracker), we should think about
updating all of the schemas to use {{<resource-manager>}} instead of
{{<job-tracker>}}. What do you all think is the best way to do this?
I'm not sure we want to completely drop {{<job-tracker>}} because I imagine
users won't like being required to change all of their workflows to
{{<resource-manager>}}. I'm thinking we should have something like this, at
least for now, and accept either in the code:
{code:xml}
<xs:choice minOccurs="1" maxOccurs="1">
<xs:element name="job-tracker" type="xs:string" minOccurs="0"
maxOccurs="1"/>
<xs:element name="resource-manager" type="xs:string" minOccurs="0"
maxOccurs="1"/>
</xs:choice>
{code}
Besides this change, we might end up having some other changes (e.g. a
dedicated field for AM Launcher memory, etc).
On schema versioning, we can either go up +0.1 on each XSD like we usually do,
or perhaps it's time to make everything 1.0?
> 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: Robert Kanter
> Attachments: OYA Scoping Doc 001.pdf, OozieYarnAM.pdf, Prelim OYA
> Scoping Doc 001.pdf, Prelim OYA Scoping Doc 002.pdf, Prelim OYA Scoping Doc
> 003.pdf, oya-rm-screenshot.jpg, oya.patch
>
>
> 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.4#6332)
