Finally, it's a milestone :) By the way, we should summarize what changed and how it affects current Oozie workflows (perhaps adding something to the Oozie website makes sense too). Right now OYA lacks good backward compatibility, which means that MR properties don't have any effect. This will change though.
Another thing that we have to agree on is patching: lots of stuff changed inside JavaActionExecutor, LauncherMapper no longer exists, etc. Therefore if someone discovers a problem in these classes (or just wants to add an improvement), it will not be possible to patch them. I suggest branching off from the commit before OYA and then we can start maintaining two branches. But this is just an idea. Peter On Fri, May 26, 2017 at 12:40 PM, Peter Cseh <gezap...@cloudera.com> wrote: > Hi everyone, > > OOZIE-1770 - Create Oozie Application Master for YARN is committed to > master! > I would like to thank the effort of everybody who was involved in the > design, the development or provided feedback in Jira or on ReviewBoard. > > This is a big change in how Oozie works and there is still a lot to do: you > can check out OOZIE-2889 for details. > > Thanks again everyone! > gp > > > -- > Peter Cseh > Software Engineer > <http://www.cloudera.com> >
