GitHub user maithtruong added a comment to the discussion: DAG not recognized. Airflow 3.1 with Docker.
Ok, so I tried the solution @potiuk gave me: - add AIRFLOW__CORE__DAG_DISCOVERY_SAFE_MODE: "False" to YAML file I also found this link: [Standalone DAG Processor Required](https://airflow.apache.org/docs/apache-airflow/stable/release_notes.html#standalone-dag-processor-required) Airflow 3.0 now requires the standalone DAG processor to parse DAGs. This dedicated process improves scheduler performance, isolation, and observability. It also simplifies architecture by clearly separating DAG parsing from scheduling logic. This change may affect custom deployments that previously used embedded DAG parsing. So I modified the YAML file as such: - add a separate airflow-init service and initialize the db using it (previously i used the api-server to initialize it) - add an airflow-dag-processor service - modify the rights so the service can access the scripts folder I still put the scripts outside of the dags/ folder because the dag processor seem to be reading from there. The DAGs are recognized now! GitHub link: https://github.com/apache/airflow/discussions/62844#discussioncomment-16019788 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
