Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.2.0
-
None
-
None
Description
Consider a WF that has four fork paths, each to a decision node, and each of these eventually in their further paths end at a single join node (thereby resulting in a valid DAG).
When such a WF is passed to Oozie and fork join validator is enabled, the validation fails cause the numForks(4) > numJoins(1). This naive way appears to be wrong to compare, and we should ideally only compare true path based forks->joins lists, if possible.
This causes a regression if the fork join validation is left enabled. Workaround for such workflows currently is to disable fork join validation via oozie.validate.ForkJoin set to false at the server.
Attachments
Attachments
Issue Links
- is duplicated by
-
OOZIE-866 forkjoin validation seems to fail if there are decision nodes in the patch
- Resolved