[
https://issues.apache.org/jira/browse/OOZIE-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated OOZIE-1034:
---------------------------------
Attachment: OOZIE-1034.patch
Disabling forkjoin validation for a workflow can now be done by putting
{code}oozie.wf.validate.ForkJoin=false{code} in your job.properties. It will
AND {{oozie.wf.validate.ForkJoin}} from the job.properties with
{{oozie.validate.ForkJoin}} from the oozie-site.xml to determine if it should
validate; in other words, they both have to be true for it to validate (both
are true by default).
> Allow disabling forkjoin validation just for a specific workflow
> ----------------------------------------------------------------
>
> Key: OOZIE-1034
> URL: https://issues.apache.org/jira/browse/OOZIE-1034
> Project: Oozie
> Issue Type: New Feature
> Components: workflow
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-1034.patch
>
>
> Currently, you can disable forkjoin validation only at the application level
> (i.e. for everything) by setting {{oozie.validate.ForkJoin}} to {{false}}.
> It would be nice to be able to do this for just for a specific workflow so
> that you don't have to disable forkjoin validation for everything if only one
> workflow requires it to be disabled; we should add a similar property in the
> job.properties file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
