[jira] [Commented] (OOZIE-1718) Coord Job Query UPDATE_COORD_JOB_CHANGE does not update last modified time

["Rohini Palaniswamy (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OOZIE-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941110#comment-13941110 ] 

Rohini Palaniswamy commented on OOZIE-1718:
-------------------------------------------

+1 Pending jenkins

> Coord Job Query UPDATE_COORD_JOB_CHANGE does not update last modified time
> --------------------------------------------------------------------------
>
>                 Key: OOZIE-1718
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1718
>             Project: Oozie
>          Issue Type: Bug
>          Components: coordinator
>    Affects Versions: trunk, 4.0.0
>            Reporter: Mona Chitnis
>            Assignee: Mona Chitnis
>             Fix For: trunk
>
>         Attachments: OOZIE-1718-0.patch, OOZIE-1718-1.patch, OOZIE-1718-2.patch, OOZIE-1718-3.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)