[
https://issues.apache.org/jira/browse/OOZIE-3588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17044489#comment-17044489
]
Junfan Zhang edited comment on OOZIE-3588 at 2/25/20 2:26 PM:
--------------------------------------------------------------
Maybe wrong code is
[here|https://github.com/apache/oozie/blob/90b9f1077d63ce9dc255f8db170b68dcb8935910/core/src/main/java/org/apache/oozie/action/oozie/SubWorkflowActionExecutor.java#L177].
The scenario is to set the retryMax parameter, but the sub workflow does not
rerun. You can reproduce this error. The real problem is that subworkflow no
reruning, not the jobid is not changed
was (Author: zuston):
Maybe wrong code is
[here|https://github.com/apache/oozie/blob/90b9f1077d63ce9dc255f8db170b68dcb8935910/core/src/main/java/org/apache/oozie/action/oozie/SubWorkflowActionExecutor.java#L177].
The scenario is to set the retryMax parameter, but the sub workflow does not
rerun. You can reproduce this error.
> Support oozie.wf.rerun.skip.nodes in subWorkflow?
> -------------------------------------------------
>
> Key: OOZIE-3588
> URL: https://issues.apache.org/jira/browse/OOZIE-3588
> Project: Oozie
> Issue Type: Bug
> Components: core
> Reporter: Junfan Zhang
> Priority: Major
>
> In Oozie code, Subworkflow support oozie.wf.rerun.failed.nodes, but don't
> support oozie.wf.rerun.skip.nodes
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
