[jira] [Comment Edited] (AIRFLOW-1715) Recognizing non-dag files as DAGs, then reporting non-existing errors

["Dmytro Kulyk (JIRA)" <ji...@apache.org>]

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

Dmytro Kulyk edited comment on AIRFLOW-1715 at 11/4/17 10:02 PM:
-----------------------------------------------------------------

i believe it have same roots with AIRFLOW-1783


was (Author: kotyara):
i beleive it have same roots with AIRFLOW-1783

> Recognizing non-dag files as DAGs, then reporting non-existing errors
> ---------------------------------------------------------------------
>
>                 Key: AIRFLOW-1715
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1715
>             Project: Apache Airflow
>          Issue Type: Bug
>    Affects Versions: Airflow 1.8
>         Environment: Ubuntu 16.04
>            Reporter: Zelko Nikolic
>
> In our DAG folder there's a few helper python files and tools. Airflow wrongly recognizes some of them as DAGs and then reports errors about them, trying to interpret them as DAGs.
> This is completely wrong. There should be a certain signature ID at the top of the file that distinguishes DAG files from other python files.
> Alternatively, there can be a workaround signature that says: "THIS IS NOT A DAG", so that Airflow can skip that file.
> For example a comment that looks like this could be such a directive:
> \#  <AIRFLOW.NOT_DAG>



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)