You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Zelko Nikolic (JIRA)" <ji...@apache.org> on 2017/10/13 22:37:00 UTC

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

Zelko Nikolic created AIRFLOW-1715:
--------------------------------------

             Summary: 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 those files 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. But there's none. So Airflow arbitrary decides which files are DAGs and which aren't. 

Please introduce a unique signature (embedded in a comment at the top of a file), like many other file formats have, because I'm sick of trying to make changes and workerounds to our helper python files so that they are not recognized as DAGs.



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