[
https://issues.apache.org/jira/browse/OOZIE-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Virag Kothari updated OOZIE-1035:
---------------------------------
Description: It seems common that users will have the "error to" transition
from every action go to the same action node (e.g. email action), which then
goes to the kill node instead of just going to the kill node directly. When
this is done in action nodes within a forkjoin path, the forkjoin validation
doesn't allow it. We should improve the forkjoin validation code to allow the
same "error to" transition, as long as it eventually leads to a kill node.
(was: It seems common that users will have the "error to" transition from every
action go to the same action node (e.g. email action), which then goes to the
kill node instead of just going to the kill node directly. When this is done
in action nodes within a forkjoin path, the forkjoin validation doesn't allow
it. We should improve the forkjoin validation code to allow the same "error
to" transition, as long as it eventually leads to a kill or end node. )
> Improve forkjoin validation to allow same errorTo transitions
> -------------------------------------------------------------
>
> Key: OOZIE-1035
> URL: https://issues.apache.org/jira/browse/OOZIE-1035
> Project: Oozie
> Issue Type: Improvement
> Components: workflow
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-1035.patch, OOZIE-1035.patch
>
>
> It seems common that users will have the "error to" transition from every
> action go to the same action node (e.g. email action), which then goes to the
> kill node instead of just going to the kill node directly. When this is done
> in action nodes within a forkjoin path, the forkjoin validation doesn't allow
> it. We should improve the forkjoin validation code to allow the same "error
> to" transition, as long as it eventually leads to a kill node.
--
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
