You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2011/09/08 06:27:09 UTC

[jira] [Commented] (OOZIE-93) GH-55: Oozie should not materialize a coordinator job right after its submission if the job will only run in far future.

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

Hadoop QA commented on OOZIE-93:
--------------------------------

rvs remarked:
Closed by f4607409376a984353e40b13f0e19ef4d1d22289 Oozie should not materialize a coordinator job right after its submission if the job will only run in far future

> GH-55: Oozie should not materialize a coordinator job right after its submission if the job will only run in far future.
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: OOZIE-93
>                 URL: https://issues.apache.org/jira/browse/OOZIE-93
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Hadoop QA
>
> Currently Oozie will materialize a coordinator job right after job submission, even if the job will only run in far future. 
> We need to modify CoordJobMatLookupCommand so that it also checks materialization's start time (set as job's start time for a newly submitted job) against current time. Only if it falls into a valid range (say, within one hour of future), we proceed with materialization.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira