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

Posted to commits@airflow.apache.org by "Dan Davydov (JIRA)" <ji...@apache.org> on 2016/05/17 20:33:12 UTC

[jira] [Updated] (AIRFLOW-126) Client facing functions should not raise exceptions but have proper exit codes

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

Dan Davydov updated AIRFLOW-126:
--------------------------------
    Description: Many client facing functions (cli) raise exceptions on failure, which is not very user friendly. It is better to define a set of exit codes that can be used on failure (sys.exit) and print out a proper message. Logging can occur to log files.  (was: Many client facing functions (cli) raise exceptions on failure, which is not very user friendly. It is better to define a set of exit codes that can be used on failure and print out a proper message. Logging can occur to log files.)

> Client facing functions should not raise exceptions but have proper exit codes
> ------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-126
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-126
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Bolke de Bruin
>
> Many client facing functions (cli) raise exceptions on failure, which is not very user friendly. It is better to define a set of exit codes that can be used on failure (sys.exit) and print out a proper message. Logging can occur to log files.



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