[ 
https://issues.apache.org/jira/browse/OOZIE-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849266#comment-15849266
 ] 

Andras Piros commented on OOZIE-1770:
-------------------------------------

Things to cover from Yahoo! meeting:
* modify code: rename {{ApplicationType}} {{Oozie Launcher}} to {{OOZIE}}
* modify JIRA: add to OOZIE-1770: benchmark results link: between regular MR, 
Uber mode MR, and OYA for workflows w/ different action types
* check: look for YARN {{ApplicationHistoryServer}} usage, whether it has 
changed from {{ApplicationTimelineServer}} and whether OOZIE-1770 changes that
* check: whether {{Credentials}} are passed correctly within 
{{JavaActionExecutor.setCredentialTokens()}}
* check: re-test that property {{launcher.lib.*}} still works
* check: that for MapReduce actions {{LauncherAM}} exits prematurely in 
circumstances where {{LauncherMapper}} did (preserve original behavior)
* check: whether generated {{launcher.xml}} file content is printed out w/ the 
launcher output

> 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)

Reply via email to