Suhas Vasu created OOZIE-1859:
---------------------------------
Summary: The API getCoordJobInfo behaves unexpectedly if the Oozie
DB is purged
Key: OOZIE-1859
URL: https://issues.apache.org/jira/browse/OOZIE-1859
Project: Oozie
Issue Type: Improvement
Reporter: Suhas Vasu
The API 'getCoordJobInfo' returns the actions for a given coordinator from a
given start action number and specified length. But if the DB tables are
purged, it returns unexpected values.
The function sets the start action number based on the the least action number
of the coordinator available in the table. So if the DB is purged, the start
action number provided is not set accordingly.
So it would be ideal, if we figure out the least available action number for a
coordinator available in the DB table and adjust the start action number
accordingly. This approach shouldn't affect the existing functionality of the
API.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
