https://dagster.io/ logo
Title
a

Aleksandr

01/25/2022, 12:39 PM
Hello! Dagster migration from 0.13.13 to 0.13.16 fails:
sqlalchemy.exc.ProgrammingError: (mysql.connector.errors.ProgrammingError) 1054 (42S22): Unknown column 'start_time' in 'field list'
Alembic migration "columns_start_time_and_end_time" file for MySQL backend remained in postgres alembic folder. The postgres alembic folder now contains two migration files: - 42add02bf976_add_columns_start_time_and_end_time.py - 713145aa999c_add_columns_start_time_and_end_time.py https://github.com/dagster-io/dagster/commit/a7b6d98b336d8530f08b1add01326d3d3df4d95e
a

Artem S

01/25/2022, 3:14 PM
Agree this. There is one possibility to get up-to-date schema for mysql - completely wipe storage.
a

alex

01/25/2022, 3:40 PM
@prha @chris
a

Artem S

01/25/2022, 4:03 PM
I also created an issue: https://github.com/dagster-io/dagster/issues/6330
❤️ 2
p

prha

01/25/2022, 5:24 PM
Yes, it looks like we accidentally created two postgres migration scripts instead of one in postgres and one in mysql