You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Venkatesh Seetharam (JIRA)" <ji...@apache.org> on 2014/03/14 00:19:46 UTC

[jira] [Commented] (FALCON-353) enable dry run feature of oozie for schedule and update

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

Venkatesh Seetharam commented on FALCON-353:
--------------------------------------------

+1 to the feature but how is this being implemented? Is this user facing or falcon uses it before its scheduled?

> enable dry run feature of oozie for schedule and update
> -------------------------------------------------------
>
>                 Key: FALCON-353
>                 URL: https://issues.apache.org/jira/browse/FALCON-353
>             Project: Falcon
>          Issue Type: Improvement
>            Reporter: Samarth Gupta
>            Assignee: Shwetha G S
>
> dry run feature of oozie enables one to test there coord before hand and verify that it conforms with the oozie syntactic and job dosent get killed on being scheduled. details here https://oozie.apache.org/docs/3.1.3-incubating/DG_CommandLineTool.html#Dryrun_of_Coordinator_Job
> we are planning to implement this via schedule and update operations in falcon  



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