[
https://issues.apache.org/jira/browse/AMATERASU-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yaniv Rodenski updated AMATERASU-66:
------------------------------------
Issue Type: New Feature (was: Bug)
> add batch directive to the maki DSL
> -----------------------------------
>
> Key: AMATERASU-66
> URL: https://issues.apache.org/jira/browse/AMATERASU-66
> Project: AMATERASU
> Issue Type: New Feature
> Reporter: Yaniv Rodenski
> Assignee: Yaniv Rodenski
> Priority: Major
> Fix For: 0.3.0-incubating
>
>
> The batch directive allows actions and flows defined under it to run in
> parallel
> Considering the following definition:
> ---
> job-name: amaterasu-test
> batch:
> - name: action1
> runner:
> group: spark
> type: jar
> artifact: ...
> - name: action2
> runner:
> group: spark
> type: jar
> artifact: ...
> ...
> action1 and action2 will be queued immediately for execution (the queueing
> order will be determined by the order of the actions in the YAML).
> *Batch and sequences:*
> a batch element can contain a seq element and also the other way round which
> will lead to the following:
> - When a sec element is queued during a batch, it will execute all of its
> internal actions in order.
> - When a batch element is queued during a sequential flow, all of its
> internal actions and sequences must complete before the next action is
> executed
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
