[
https://issues.apache.org/jira/browse/OOZIE-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264219#comment-14264219
]
ronan stokes commented on OOZIE-2056:
-------------------------------------
It might be useful to have a further enhancement to support spawning of
multiple workflows with waiting for completeness as optional.
The scenario I am thinking is when processing multiple datasets and you want to
launch a sub workflow for each dataset.
The subworkflows could each be given a different data input based on a list of
data values passed as part of the subworkflow definition.
For example, the call to launch the subworkflow could specify something like
<data-inputs separator="," param="data-input" >
... inputs as comma delimited set of paths ...
</data-input>
This would effectively provide a looping mechanism of the form " for x in list
do workflow y".
The purpose of the param attribute would be to specify the name of the
parameter in the subworkflow
> Add an option to make the subworkflow action not wait
> -----------------------------------------------------
>
> Key: OOZIE-2056
> URL: https://issues.apache.org/jira/browse/OOZIE-2056
> Project: Oozie
> Issue Type: New Feature
> Reporter: Robert Kanter
>
> Currently, a workflow waits for a subworkflow to finish before continuing.
> It may be useful to have an option in the subworkflow action to not wait
> (similar to blocking vs non-blocking I/O).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
