[
https://issues.apache.org/jira/browse/FALCON-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705563#comment-14705563
]
Ajay Yadava commented on FALCON-1174:
-------------------------------------
On debugging [~jaydeepvishwakarma] found that the actual issue is that during
dryRun Oozie is actually looking for an instance path which can match to
latest(0) (any instance) and it doesn't find any and being a synchronous
operation it fails. If a feed instance is created/exists then the issue goes
away. We tested this with feeds with existing instances and same consumer
process worked smoothly.
That said it is not always possible to wait for feed instances to be available
or bootstrap with a dummy one and this feature will be useful in those cases.
> 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)
