InMobi/oozie — pull request #11 by shwethags (2014-01-28 10:06:15+00:00)
Title: FALCON-44 Prepare for oozie internal release

Merged the following:
* PollablePriorityDelayQueue.poll() returns elements with +ve delay - https://issues.apache.org/jira/browse/OOZIE-1664
* Coordinators that undergo change endtime but are doneMaterialization, not getting picked for StatusTransit - https://issues.apache.org/jira/browse/OOZIE-1632
* IllegalArgumentException: wfId cannot be empty - https://issues.apache.org/jira/browse/OOZIE-1314
* Allow re-run of actions of killed coordinator - https://issues.apache.org/jira/browse/OOZIE-1562
* Oozie coordinator job with identical start and end time remains "RUNNING" forever - https://issues.apache.org/jira/browse/OOZIE-1577
* RecoveryService keeps repeatedly queueing SuspendXCommand - https://issues.apache.org/jira/browse/OOZIE-1545
* Load more coordinator jobs eligible to be materialized in MaterializeTriggerService - https://issues.apache.org/jira/browse/OOZIE-1539
* A CoordActionUpdateXCommand gets queued for all workflows even if they were not launched by a coordinator - https://issues.apache.org/jira/browse/OOZIE-1448
* Command queue filling up with duplicate commands from RecoveryService - https://issues.apache.org/jira/browse/OOZIE-1507
* getKey() not overridden in some commands causing duplicates in queue - https://issues.apache.org/jira/browse/OOZIE-1473
* BundleStatusUpdateXCommand should get lock for bundle job - https://issues.apache.org/jira/browse/OOZIE-1470
* Duplicate Coord_Action events on Waiting -> Timeout, and Coord Materialize not removing actions on Failure - https://issues.apache.org/jira/browse/OOZIE-1450
* Job materialization happening even after coordinator is supposed to be killed. - https://issues.apache.org/jira/browse/OOZIE-1439
* Two workflow jobs mapped to a single coordinator action - https://issues.apache.org/jira/browse/OOZIE-1272