You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Victor Villas Bôas Chaves (JIRA)" <ji...@apache.org> on 2019/08/13 12:10:00 UTC
[jira] [Created] (AIRFLOW-5198) Avoid loading DAGs during migration
cc1e65623dc7_add_max_tries_column_to_task_instance
Victor Villas Bôas Chaves created AIRFLOW-5198:
--------------------------------------------------
Summary: Avoid loading DAGs during migration cc1e65623dc7_add_max_tries_column_to_task_instance
Key: AIRFLOW-5198
URL: https://issues.apache.org/jira/browse/AIRFLOW-5198
Project: Apache Airflow
Issue Type: Improvement
Components: database
Affects Versions: 1.10.4
Reporter: Victor Villas Bôas Chaves
https://issues.apache.org/jira/browse/AIRFLOW-1366 introduced a migration to add a `max_tries` column to the `task_instance` table.
Currently, that migration imports and instantiates the `DagBag` object, which will load example DAGs if the setting is activated, and will fail. It fails because at this point because loading DAGs requires later migrations to have been run.
A simple fix would be to force `{color:#e01e5a}include_examples=False{color}` in the DagBag, but we should strive not lot load DAGs at all and only retrieve the necessary data for the migration.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)