Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
trunk, 4.0.0
-
None
Description
The update query - 'UPDATE_COORD_JOB_CHANGE' in CoordJobQueryExecutor fails to update the job's last modified timestamp. Hence it gets reset to null in database. This causes errors in future materialization of the job where jobs are retrieved in order of their last modified time.
Patch also includes related fix where CoordKillXCommand will now fetch last modified time (via GET_GET_COORD_JOB_SUSPEND_KILL) so that its update command does not overwrite last modified time to NULL.
Attachments
Attachments
Issue Links
- is duplicated by
-
OOZIE-1742 CoordChangeXCommand doesn't update LastModifiedTime properly
- Resolved