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

Jeremiah Lowin edited comment on AIRFLOW-64 at 5/6/16 10:35 PM:
----------------------------------------------------------------

I agree -- would you mind making a PR? 

PRs will still go through GitHub but must reference a JIRA issue in the title. 
For example:
"\[AIRFLOW-64\] Add note about relative DAGS_FOLDER"

Thanks!d


was (Author: jlowin):
I agree -- would you mind making a PR? 

PRs will still go through GitHub but must reference a JIRA issue in the title. 
For example, "[AIRFLOW-64] Add note about relative DAGS_FOLDER".

Thanks!

> dags_folder not handled correctly
> ---------------------------------
>
>                 Key: AIRFLOW-64
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-64
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: cli, executor, scheduler
>    Affects Versions: Airflow 1.7.0
>         Environment: running on mac os X
> airflow.cfg:
> ```
> airflow_home = .
> dags_folder = ./dags
> ```
>            Reporter: Giacomo Tagliabe
>
> running `airflow list_dags` with the command above from a location with a 
> `dags` subdirectory, the cli erros the following message:
> ```
> airflow.utils.AirflowException: subdir has to be part of your DAGS_FOLDER as 
> defined in your airflow.cfg
> ```
> if I change the airflow.cfg to `dags_folder = dags`, list_dags seem to work 
> correctly, but any other task doesn't seem to handle the dags_folder 
> correctly. Here is what `airflow scheduler` outputs when it tries to execute 
> a scheduled dag:
> ```
> DAG [process_deleted_runs] could not be found in 
> /Users/giacomo/workspace/qsi/scheduler/dags/Users/giacomo/workspace/qsi/scheduler/process_deleted_runs.py
> ```
> As you see, it seems that the absolute path 
> (`/Users/giacomo/workspace/qsi/scheduler/`) is chained twice.



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

Reply via email to