You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@amaterasu.apache.org by "Yaniv Rodenski (JIRA)" <ji...@apache.org> on 2018/02/18 08:10:00 UTC

[jira] [Updated] (AMATERASU-6) Long running actions/pipelines

     [ https://issues.apache.org/jira/browse/AMATERASU-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yaniv Rodenski updated AMATERASU-6:
-----------------------------------
    Affects Version/s: 0.3.0-incubating

> Long running actions/pipelines 
> -------------------------------
>
>                 Key: AMATERASU-6
>                 URL: https://issues.apache.org/jira/browse/AMATERASU-6
>             Project: AMATERASU
>          Issue Type: New Feature
>    Affects Versions: 0.3.0-incubating
>            Reporter: Yaniv Rodenski
>            Priority: Major
>
>  As a pipeline developer, I can define pipelines and actions to be long-running, for workloads such as stream processing etc. 
> Example maki.yml
> job-name:    amaterasu-test
> type: long-running
> flow:
>    - name: action1
>      type: long-running
>      runner:
>          group: spark
>          type: scala       
>      file: src/file.scala
>      exports:
>          oddData: parquet



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)