Skip to content

Use initdb instead of migratedb to handle database initialization/upgrade #223

@FrancisLee13

Description

@FrancisLee13

Overview

Currently, the database initialization/upgrade is done by calling airflow's migratedb in db_command.py. migratedb internally calls airflow's upgradedb, which has more parameters than initdb does, including some parameters with default values. Using migratedb requires us to provide all of parameters, and we also need to make sure the parameters we provide are consistent across airflow versions, whereas using initdb we don't need to provide any parameters, and we can depend on the default(which is, in most cases, recommended) behaviour of airflow when doing db migration/initialization.

Acceptance Criteria

In the next version release, change the migratedb call to initdb in file <version>/python/database/migrate.py

Additional Info

<Optional if you have additional info/context that you are useful to attach>

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions