You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2012/10/25 22:23:12 UTC
[jira] [Created] (OOZIE-1034) Allow disabling forkjoin validation
just for a specific workflow
Robert Kanter created OOZIE-1034:
------------------------------------
Summary: 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
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
[jira] [Updated] (OOZIE-1034) Allow disabling forkjoin validation
just for a specific workflow
Posted by "Robert Kanter (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (OOZIE-1034) Allow disabling forkjoin validation
just for a specific workflow
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485363#comment-13485363 ]
Hadoop QA commented on OOZIE-1034:
----------------------------------
Testing JIRA OOZIE-1034
Cleaning local svn workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:green}+1{color} the patch does not introduce any line longer than 132
. {color:green}+1{color} the patch does adds/modifies 2 testcase(s)
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT warnings
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc warnings
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
. {color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations
. {color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
. Tests run: 915
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/159/
> 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
[jira] [Commented] (OOZIE-1034) Allow disabling forkjoin validation
just for a specific workflow
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502326#comment-13502326 ]
Alejandro Abdelnur commented on OOZIE-1034:
-------------------------------------------
+1
> 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
[jira] [Commented] (OOZIE-1034) Allow disabling forkjoin validation
just for a specific workflow
Posted by "Robert Kanter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502347#comment-13502347 ]
Robert Kanter commented on OOZIE-1034:
--------------------------------------
Committed to trunk
> 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