[ https://issues.apache.org/jira/browse/AMATERASU-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yaniv Rodenski updated AMATERASU-7: ----------------------------------- Description: As a pipeline developer, I can define a schedule in the maki.yml for my pipeline to run. I can also define a schedule for an action in a long-running pipeline 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 - name: action2 type: scheduled schedule: 10 * * * * runner: group: spark type: python file: src/file2.scala imports: oddData: parquet file: file2.py was: As a pipeline developer, I can define a schedule in the maki.yml for my pipeline to run. I can also define a schedule for an action in a long-running pipeline 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 - name: action2 *type: scheduled schedule: 10 * * * * * runner: group: spark type: python file: src/file2.scala imports: oddData: parquet file: file2.py > Scheduled pipelines/actions > --------------------------- > > Key: AMATERASU-7 > URL: https://issues.apache.org/jira/browse/AMATERASU-7 > Project: AMATERASU > Issue Type: New Feature > Reporter: Yaniv Rodenski > > As a pipeline developer, I can define a schedule in the maki.yml for my > pipeline to run. I can also define a schedule for an action in a long-running > pipeline > 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 > - name: action2 > type: scheduled > schedule: 10 * * * * > runner: > group: spark > type: python > file: src/file2.scala > imports: > oddData: parquet > file: file2.py -- This message was sent by Atlassian JIRA (v6.4.14#64029)