Does this mean we'll need an RC3 to include OOZIE-1514? thanks - Robert
On Mon, Aug 26, 2013 at 10:54 AM, Mona Chitnis <[email protected]> wrote: > Thanks for the clarification Bowen. I was able to reproduce the issue and > opening a blocker JIRA. > > > > Mona Chitnis > Software Engineer, Hadoop Team > Yahoo! > > > ________________________________ > From: bowen zhang <[email protected]> > To: Mona Chitnis <[email protected]>; "[email protected]" < > [email protected]>; "[email protected]" <[email protected]> > Sent: Monday, 26 August 2013 10:42 AM > Subject: Re: [VOTE] Release Oozie 4.0.0 (RC2) > > > Hi Mona, > I don't see how "coordAction.getMissingDependencies() is NULL" when you > rerun it. Since the first time when you normally run the action, the if > statement resolves to true and the line > "coordAction.setMissingDependencies(nonExistListStr);" sets the > MissingDependencies to empty string. So, when you rerun a particular > action, the two strings are both empty, making the if statement evaluate to > false. The unit test you mentioned does not test rerun command. > Bowen > > > > > ________________________________ > From: Mona Chitnis <[email protected]> > To: "[email protected]" <[email protected]>; "[email protected]" > <[email protected]>; bowen zhang <[email protected]> > Sent: Monday, August 26, 2013 10:13 AM > Subject: Re: [VOTE] Release Oozie 4.0.0 (RC2) > > > > This case - Rerun or Change command on a coordinator with no input > dependencies - has been tested specifically. In this case, missDeps = > coordAction.getMissingDependencies() is NULL, whereas nonExistList is > EMPTY. The if condition you mentioned thus resolves to true, and the > correct Db update executor - CoordActionUpdateForInputCheckJPAExecutor is > executed. > > You can run an example or the unit test - > TestCoordActionInputCheckXCommand#testNoDatasetDependency to test it out. > > Regards, > > > > Mona Chitnis > Software Engineer, Hadoop Team > Yahoo! > > > ________________________________ > From: bowen zhang <[email protected]> > To: "[email protected]" <[email protected]>; Mona Chitnis < > [email protected]>; "[email protected]" <[email protected]> > Sent: Friday, 23 August 2013 5:08 PM > Subject: Re: [VOTE] Release Oozie 4.0.0 (RC2) > > > rerun oozie coordinator action that has no data dependency will make the > action stuck in "WAITING" forever. > The issue has to do with the change introduced in > coordActionInputCheckXCommand. The rerun action will fail this if statement: > if (!nonExistListStr.equals(missingDeps)) > since nonExistListStr and missingDeps are both empty strings. Once it > fails the if statement, isChangeDependency is still > set to false and the status change to "READY" will not be persisted since > we will call CoordActionUpdateForModifiedTimeJPAExecutor instead of > CoordActionUpdateForInputCheckJPAExecutor in the updateCoordAction method. > the Action is in "WAITING" stage forever. > > > > > ________________________________ > From: Ryota Egashira <[email protected]> > To: "[email protected]" <[email protected]>; Mona Chitnis < > [email protected]>; "[email protected]" <[email protected]> > Sent: Friday, August 23, 2013 2:23 PM > Subject: Re: [VOTE] Release Oozie 4.0.0 (RC2) > > > +1 > > -verified md5 > -built and started oozie-server > -ran examples on hadoop-1.1.1 cluster > -checked SLA examples and UI > > Thanks > Ryota > > On 8/23/13 10:36 AM, "Mona Chitnis" <[email protected]> wrote: > > >Hello Oozie community, > > > > > >The release candidate 2 for Oozie 4.0.0 is available. (Critical bug fixes > >from RC1 and excluding 'workflowgenerator' from release tarball) > > > >Recap from previous 4.0.0 RCs, > > > >Oozie 4.0.0 has major features such as Hcatalog Integration, SLA > >Monitoring (with Dashboard in UI) and JMS Messaging. It has several other > >important bug fixes. You can refer to the release-log.txt for all > the > >features and fixes. > > > >Keys to verify the signature of the release artifact are available at > >http://www.apache.org/dist/oozie/KEYS > > > >Please download, try out the release, and vote by replying on the thread: > >http://people.apache.org/~mona/oozie-4.0.0-rc2 > > > >The release, md5 signature, gpg signature, and rat report can all be > >found at the above address. > > > >Note: This release also has a database schema change with additional > >tables and columns, so run the DB creation tool. > >Below are the incompatible changes in this release: > > > >OOZIE-1408 Change column type of "frequency" from int to varchar for > >coordinators > >OOZIE-1357 Can't view more than 1000 actions of a coordinator and paging > >does not > work > >OOZIE-1231 Provide access to launcher job URL from web console when using > >Map Reduce action > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20OOZIE%20AND%20l > >abels%20%3D%20incompatible > > > >Also, > >If you are checking out the HCatalog integration functionality, refer to > >HCatalog installation instructions at - > >http://hive.apache.org/docs/hcat_r0.5.0/install.html > >And, ActiveMQ (JMS-compliant message broker) installation instructions at > >- http://activemq.apache.org/getting-started.html > >The Oozie server settings required are enlisted in the Oozie install > >documentation > itself. > > > > > >Vote closes after 3 business days on Aug 27 11:00 PDT. > > > > > > > >Thanks, > > > >Mona Chitnis >
