Delete dag_version table when downgrading the DB from the versioned Airflow#44397
Merged
ephraimbuddy merged 1 commit intoapache:mainfrom Nov 27, 2024
Merged
Delete dag_version table when downgrading the DB from the versioned Airflow#44397ephraimbuddy merged 1 commit intoapache:mainfrom
dag_version table when downgrading the DB from the versioned Airflow#44397ephraimbuddy merged 1 commit intoapache:mainfrom
Conversation
potiuk
approved these changes
Nov 27, 2024
… Airflow In dagcode, fileloc_hash column was a primary key on the version before dag versioning. If dagcode is not deleted before downgrading, the fileloc_hash column, created when downgrading, would be a null column that can't be used for a primary key. A similar thing applies to serialized dag, which would have duplicates, and the primary key can't be determined. The solution is to delete the dag_version table data, which will delete the serdag and dagcode table data
b9f8b0e to
9dbdfce
Compare
ArshiaZr
pushed a commit
to ArshiaZr/airflow
that referenced
this pull request
Nov 27, 2024
… Airflow (apache#44397) In dagcode, fileloc_hash column was a primary key on the version before dag versioning. If dagcode is not deleted before downgrading, the fileloc_hash column, created when downgrading, would be a null column that can't be used for a primary key. A similar thing applies to serialized dag, which would have duplicates, and the primary key can't be determined. The solution is to delete the dag_version table data, which will delete the serdag and dagcode table data
got686-yandex
pushed a commit
to got686-yandex/airflow
that referenced
this pull request
Jan 30, 2025
… Airflow (apache#44397) In dagcode, fileloc_hash column was a primary key on the version before dag versioning. If dagcode is not deleted before downgrading, the fileloc_hash column, created when downgrading, would be a null column that can't be used for a primary key. A similar thing applies to serialized dag, which would have duplicates, and the primary key can't be determined. The solution is to delete the dag_version table data, which will delete the serdag and dagcode table data
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In dagcode, fileloc_hash column was a primary key on the version before dag versioning. If dagcode is not deleted before downgrading, the fileloc_hash column, created when downgrading, would be a null column that can't be used for a primary key. A similar thing applies to serialized dag, which would have duplicates, and the primary key can't be determined. The solution is to delete the dag_version table data, which will delete the serdag and dagcode table data