Hi Angelo, I think my part looks fine.
Thanks, Kiran On Tue, Sep 20, 2011 at 11:17 AM, Mona Chitnis <[email protected]>wrote: > There is a duplicate JIRA OOZIE-550 and OOZIE-2 both regarding the fix to > the ‘fs move’ action being inconsistent. 550 mentions resolution as > ‘wont-fix’ and 2 mentions resolution as ‘fixed’. The correct status should > be ‘fixed’ and these JIRAs should be consolidated. > > --Mona Chitnis > > > > On 9/20/11 11:10 AM, "Angelo K. Huang" <[email protected]> wrote: > > Hi All, > > This is Oozie release list for 3.1. Please review it. Thanks. > > OOZIE-37 Documentation related modifications for "log -action" option > OOZIE-35 add auto-rerun for error codes JA008 and JA009 in action executor > OOZIE-21 Fixed bug forked subwf not returning status to the parent wf job > OOZIE-28 update coordinator name to coord job at loadstate of coord-submit > to avoid exception of bundle-status-update > OOZIE-22 (Apache) Add support PostgreSQL > OOZIE-10 add user-retry in workflow action > OOZIE-540 CoordKillXCommand command uniqueness and increase priority > OOZIE-552 support multiple shared lib path in oozie > OOZIE-18 Option to view Workflow job details from Coordinator job detail > popup > OOZIE-17 Group column for coordinator jobs in Oozie Web Console > OOZIE-11 Adding Distcp Action. > OOZIE-6 Custom filters option and User information column added to > Coordinator jobs section of Oozie Web Console > OOZIE-5 Log retrieval for a Coordinator job with large number or actions > OOZIE-7 Ability to view the log information corresponding to particular > coordinator actions > OOZIE-541: Update documentation for job-type in WS API > OOZIE-498: Add an email action to Oozie* > *OOZIE-518: merge changes for OOZIE-101 to ActionEndXCommand > OOZIE-529: workflow kill node message is not resolved and set it to action > error message > OOZIE-528: adjust configuration for DBCP data source* > *OOZIE-522: migrate jpa service changes to master branch from integration > branch* > *OOZIE-520: upgrade openjpa jar to 2.1.0* > *OOZIE-527: add coordinator 0.3 schema for app name parametrization* > *OOZIE-518:* *${wf:lastErrorNode()} is not set when an action ends in error > OOZIE-516 action errorMessage is not being set > OOZIE-524 add test case to test uniqueness of CoordActionInputCheckXCommand > OOZIE-517 escape characters for xml when create dag evaluator > OOZIE-515 parametrization of 'name' attribute in > workflow/coordinator/bundle > OOZIE-523 add new queue class to iterate next callable when current > callable > type has reached max concorrency > OOZIE-525 Upgrade pom version to 3.1.0. > OOZIE-550 Fs 'move' action made consistent and able to have existing target > dir > OOZIE-417 oozie-stop.sh is oblivious to 'catalina.sh stop' failing > > > -- > *mona > **chitnis > *software developer > > [email protected] > direct 408-336-7908 mobile 864-650-0100 > > 701 first avenue, sunnyvale, ca, 94089-0703, us > phone (408) 349 3300 fax (408) 349 3301 > > >
