[
https://issues.apache.org/jira/browse/FALCON-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544888#comment-14544888
]
Pallavi Rao commented on FALCON-1174:
-------------------------------------
[~sowmyaramesh], agree that this is nice to have and might be a easy workaround
for bugs in dry run of Oozie. But, I am not convinced that this has to be a
runtime property. And here is my reasoning: Generally, administrators/ops will
manage runtime properties and it is meant to be global. If one user needs to
turn off dry run for one particular process, he shouldn't have to reach out to
ops to turn that flag off and back on once he has scheduled his process. It
would be better if a user can specify a flag in the request, while scheduling a
process.
> Ability to disable oozie dryrun while scheduling or updating the falcon entity
> ------------------------------------------------------------------------------
>
> Key: FALCON-1174
> URL: https://issues.apache.org/jira/browse/FALCON-1174
> Project: Falcon
> Issue Type: Improvement
> Components: oozie
> Affects Versions: 0.6
> Reporter: Sowmya Ramesh
> Assignee: Sowmya Ramesh
> Fix For: 0.7
>
> Attachments: FALCON-1174.v0.patch
>
>
> Today, before scheduling or updating an entity Oozie dry run is done to
> validate it. This validation helps as Oozie dry run is s a sync operation and
> hence validation can be done before scheduling the job.
> There may be a requirement where user would want to turn off this feature.
> Improvement is to provide a config knob to skip the dry run.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
