You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Mona Chitnis (JIRA)" <ji...@apache.org> on 2014/02/28 04:47:19 UTC

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

     [ https://issues.apache.org/jira/browse/OOZIE-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mona Chitnis updated OOZIE-1718:
--------------------------------

    Attachment: OOZIE-1718-0.patch

attaching patch. testcase in TestBundleChangeXCommand is wip - minor tweaks reqd. please review

> Coord Job Query UPDATE_COORD_JOB_CHANGE does not persist 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
>
>   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



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)