aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AURORA-262) "Nothing to do, don't execute dependencies" flag for a Process
Date Mon, 28 Dec 2015 02:20:49 GMT

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

Bill Farner resolved AURORA-262.
--------------------------------
    Resolution: Won't Fix

> "Nothing to do, don't execute dependencies" flag for a Process
> --------------------------------------------------------------
>
>                 Key: AURORA-262
>                 URL: https://issues.apache.org/jira/browse/AURORA-262
>             Project: Aurora
>          Issue Type: Story
>          Components: Executor
>            Reporter: Kevin Sweeney
>            Priority: Minor
>
> I've been writing a lot of thermos recently and one feature would make my life much easier:
> my (simplified) process graph
> {code}
> copy_input_data -> generate_output_data_from_input_data -> copy_output_data
> {code}
> I'd like to add conditional logic to this graph to prevent unnecessary work. This is
easily possible by adding a new process to the start of the graph
> {code}
> check_output_exists = Process(
>   cmdline="""if output_exists; then exit 1; else exit 0; fi""")
> {code}
> This successfully aborts the pipeline but tells the executor that the task has failed,
which will cause the scheduler to retry forever. An alternative would be to add this conditional
logic to every dependency process in the pipeline (and exit 0) but that gets pretty messy.
I propose adding a new feature to thermos that allows a Process to skip the rest of the graph,
but still indicate success.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message