I was hoping one of our QA engineers would take care of that, but it looks like he won't have time. I don't think I'm proficient enough in Hive Server 2 to make the example, so I've unassigned OOZIE-1963 from me. Though I think it would still be good to include.
If we include the Spark action, I think we should also include OOZIE-2170. OOZIE-2174 would also be good; it addresses some long-standing shortcomings of OozieClient/OozieCLI. Finally, we should also include OOZIE-2181, which fixes some problems retrieving job info. I have patches available for all 3 of these. - Robert On Wed, Mar 25, 2015 at 10:58 AM, Shwetha Shivalingamurthy < [email protected]> wrote: > Robert, will you be able to take up OOZIE-1963? > > Dev team, Are there any other un-resolved jiras that needs to be part of > 4.2 release? > > Thanks, > Shwetha > > > On 11/02/15 1:44 pm, "Robert Kanter" <[email protected]> wrote: > > >I 4.2.0 release sounds good; I don't have cycles to drive it though. > > > >The Spark action currently has a number of problems with it. I'd hold off > >on putting that into a release until we get those fixed (OOZIE-2071 > ><https://issues.apache.org/jira/browse/OOZIE-2071> (it's to add an > >example, > >but the comments discuss the problems), OOZIE-2087 > ><https://issues.apache.org/jira/browse/OOZIE-2087>). > > > >I'm all for including the Hive2 action; though it would be good if we > >could > >create an example workflow for it for completeness (OOZIE-1963 > ><https://issues.apache.org/jira/browse/OOZIE-1963>). I can probably take > >care of this relatively easily. > > > > > >- Robert > > > >On Tue, Feb 10, 2015 at 9:56 PM, Shwetha Shivalingamurthy < > >[email protected]> wrote: > > > >> Hi All, > >> > >> Oozie trunk has a couple of changes since the last oozie release - > >>re-run > >> fixes, config cleanup, spark action, hive2 action, external > >>configuration > >> for mapred action, better error reporting and many other bug fixes. > >> > >> Can we have a oozie release from trunk? If someone wants to volunteer to > >> drive the release, please take this forward. Else, I can drive it as > >>well. > >> > >> If we want to do a release, let's identify the pending jiras which are > >> required for this release. > >> > >> Thanks, > >> Shwetha > >> > >
