You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2018/09/02 18:01:02 UTC

[jira] [Commented] (AIRFLOW-2608) Improved Exceptions handling in APIs

    [ https://issues.apache.org/jira/browse/AIRFLOW-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16601395#comment-16601395 ] 

Apache Spark commented on AIRFLOW-2608:
---------------------------------------

User 'verdan' has created a pull request for this issue:
https://github.com/apache/incubator-airflow/pull/3496

> Improved Exceptions handling in APIs
> ------------------------------------
>
>                 Key: AIRFLOW-2608
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2608
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Verdan Mahmood
>            Assignee: Verdan Mahmood
>            Priority: Major
>              Labels: exception-handling
>             Fix For: 1.10.0, 2.0.0
>
>
> The error handling in APIs is very poor, and most of the exceptions are raised directly from AirflowExceptions which is the base exceptions class. 
> Also, some of the custom exceptions are created locally under the scope of each file making it duplicated for other files. 
> We should have a centralized location for Exception classes along with the standard default message for each exception. 



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