uranusjr edited a comment on issue #18939: URL: https://github.com/apache/airflow/issues/18939#issuecomment-944973055
I think you get what you see because MySQL lacks DDL transaction, so when migration failed on line 140, the database is stuck in an awkward state that the migration is half finished. This is a very common problem with schema migrations on MySQL. The "good" thing is (if we can say anything is good from the situation), since you are stuck right between lines 139 and 140, you are now in a perfect position to debug the situation and figure out what exactly causes line 140 to fail, and if you managed to figure out a way to fix that line, that'd be our desired solution. The error message provided by Alembic is quite unhelpful, unfortunately (which is not uncommon for Alembic/SQLAlchemy in general, which I lament), but the code itself is pretty description by itself. But we need to figure out why that fails (and why on earth does Alembic even want to drop the `run_id` column in the first place when we ask it to create a unique constraint). (Actual line added for reference) https://github.com/apache/airflow/blob/5dd690b57a20ca944deb8d96e89ec6ae6161afeb/airflow/migrations/versions/7b2661a43ba3_taskinstance_keyed_to_dagrun.py#L126-L140 -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
