b-anantha commented on issue #29836: URL: https://github.com/apache/superset/issues/29836#issuecomment-2860963143
Ran into the same issue today and it looks like the problem is due to two migration versions being merged in that were lower in place than the previous head of an older release. [3.0.1 head 2023-09-15_12-58 4b85906e5b91](https://github.com/apache/superset/blob/3.0.1/superset/migrations/versions/2023-09-15_12-58_4b85906e5b91_add_on_delete_cascade_for_dashboard_roles.py) [4.0.2 head 2024-02-14_14-43 17fcea065655](https://github.com/apache/superset/blob/4.0.2/superset/migrations/versions/2024-02-14_14-43_17fcea065655_change_text_to_mediumtext.py) The two that were merged in between these two versions but did not increment are [2023-07-12_20-34_e0f6f91c2055_create_user_favorite_table.py](https://github.com/apache/superset/blob/4.0.1/superset/migrations/versions/2023-07-12_20-34_e0f6f91c2055_create_user_favorite_table.py) [2023-07-19_17-54_ee179a490af9_deckgl_path_width_units.py](https://github.com/apache/superset/blob/4.0.1/superset/migrations/versions/2023-07-19_17-54_ee179a490af9_deckgl_path_width_units.py) I was able to work past this by just running those two versions. ```shell # We get the current version of the database > $ superset db current 17fcea065655 (head) # Set the alembic_version.version_num to the first version that was merged in between the releases > $ superset db stamp bf646a0c1501 INFO [alembic.runtime.migration] Running stamp_revision 17fcea065655 -> bf646a0c1501 # Upgrade to the second version that was merged in between the releases, this works since there are adjacent versions > $ superset db upgrade ee179a490af9 INFO [alembic.runtime.migration] Running upgrade bf646a0c1501 -> e0f6f91c2055, create_user_favorite_table INFO [alembic.runtime.migration] Running upgrade e0f6f91c2055 -> ee179a490af9, deckgl-path-width-units # Set the alembic_version.version_num back to what it was so future upgrades progress naturally > $ superset db stamp 17fcea065655 INFO [alembic.runtime.migration] Running stamp_revision ee179a490af9 -> 17fcea065655 ``` A check for ensuring that any new migrations/versions that are not newer than the latest one in master should probably prevent PR from merging. It's not so much a problem within a release but if it crosses a release line then we can get things like this. -- 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: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
