kaxil opened a new pull request #13893: URL: https://github.com/apache/airflow/pull/13893
closes https://github.com/apache/airflow/issues/13504 Currently the DagFileProcessor parses the DAG files, writes it to the `dag` table and then writes DAGs to `serialized_dag` table. At the same time, the scheduler loop is constantly looking for the next DAGs to process based on ``next_dagrun_create_after`` column of the DAG table. It might happen that as soon as the DagFileProcessor writes DAG to `dag` table, the scheduling loop in the Scheduler picks up the DAG for preocessing. However, as the DagFileProcessor has not written to serialized DAG table yet the scheduler will error with "Serialized Dag not Found" error. This would mainly happen when the DAGs are dynamic where the result of one DAG, creates multiple DAGs. This commit changes the order of writing DAG and Serialized DAG and hence before a DAG is written to `dag` table it will be written to `serialized_dag` table. <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md). ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
