[
https://issues.apache.org/jira/browse/AIRFLOW-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16767296#comment-16767296
]
Daniel Lamblin edited comment on AIRFLOW-1715 at 2/13/19 3:20 PM:
------------------------------------------------------------------
I think you'll find the existing affordance of correctly [using a filename
pattern in an ignore
file|https://airflow.apache.org/concepts.html#airflowignore] to be sufficient
for your needs however.
It wasn't as clearly documented for <v1.9 though it existed for a long while.
was (Author: dlamblin):
I think you'll find the existing affordance of correctly [using a filename
pattern in an ignore
file|https://airflow.apache.org/concepts.html#airflowignore] to be sufficient
for your needs however.
> 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: 1.8.0
> Environment: Ubuntu 16.04
> Reporter: Zelko Nikolic
> Priority: Major
>
> 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
(v7.6.3#76005)
