[
https://issues.apache.org/jira/browse/OOZIE-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764535#comment-15764535
]
Peter Bacsko commented on OOZIE-1770:
-------------------------------------
For some reason there are a bunch of finbugs issues which are reported as new
but they are not. When the patch is compiled, even classes that were not
modified are reported as faulty. I decided to address all these problems,
except two: a {{toString()}} which uses {{keySet()}} instead of {{entrySet()}},
because it's a complicated map-of-maps. The second is {{eventService}} inside
{{XCommand}} - I wanted to change it from static to non-static but this caused
all sort of compilation problems in different XCommand classes and I don't
think it's worth doing it just for the sake of fingbugs. So I ignored these two.
> 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, 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)
