ozw1z5rd commented on issue #10154:
URL: https://github.com/apache/airflow/issues/10154#issuecomment-682380876
@kaxil on my production installation, the list has different order.
```
<class 'airflow.models.dag.DagModel'>,
<class 'airflow.models.dag.DagTag'>,
```
in your list:
```
<class 'airflow.models.dag.DagTag'>,
<class 'airflow.models.dag.DagModel'>,
```
I did not dive in deep, however I think this problem raises _because of the
upgrade_ from airflow 1.9.0 to 1.10.10. The upgradedb did not run in
production, it ran in staging and later all the differences have been moved by
DBA teams on the production db.
```
>>> pprint.pprint(list(models.base.Base._decl_class_registry.values()))
[<class 'airflow.models.dagrun.DagRun'>,
<class 'airflow.models.xcom.XCom'>,
<class 'airflow.models.log.Log'>,
<class 'airflow.models.kubernetes.KubeResourceVersion'>,
<class 'airflow.models.taskfail.TaskFail'>,
<class 'airflow.models.kubernetes.KubeWorkerIdentifier'>,
<class 'airflow.jobs.base_job.BaseJob'>,
<class 'airflow.models.knownevent.KnownEvent'>,
<class 'airflow.jobs.backfill_job.BackfillJob'>,
<class 'airflow.models.taskinstance.TaskInstance'>,
<class 'airflow.models.chart.Chart'>,
<class 'airflow.models.errors.ImportError'>,
<class 'airflow.models.dagpickle.DagPickle'>,
<class 'airflow.models.user.User'>,
<class 'airflow.models.dag.DagModel'>,
<class 'airflow.models.variable.Variable'>,
<class 'airflow.models.pool.Pool'>,
<class 'airflow.models.dagcode.DagCode'>,
<class 'airflow.models.slamiss.SlaMiss'>,
<class 'airflow.models.connection.Connection'>,
<class 'airflow.jobs.local_task_job.LocalTaskJob'>,
<class 'airflow.models.dag.DagTag'>,
<sqlalchemy.ext.declarative.clsregistry._ModuleMarker object at 0x29b96b0>,
<class 'airflow.models.knownevent.KnownEventType'>,
<class 'airflow.models.renderedtifields.RenderedTaskInstanceFields'>,
<class 'airflow.jobs.scheduler_job.SchedulerJob'>,
<class 'airflow.models.taskreschedule.TaskReschedule'>]
```
----------------------------------------------------------------
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]
