b-anantha commented on issue #29836:
URL: https://github.com/apache/superset/issues/29836#issuecomment-2863987836
That is pretty much how I was able to reproduce in development and test the
"fix" before trying it in our staging environment. Holding off on doing the
same in production for a bit to get feedback on the problem.
1. Pull tag 3.0.1, build, and start
a. This will set the alembic version to 4b85906e5b91
2. Pull tag 4.0.2, build, and start
a. This will start the upgrade from 4b85906e5b91 to 17fcea065655 and
skip e0f6f91c2055 and ee179a490af9
The head of 2.1.3 is 2023-05-01_12-03_9c2a5681ddfd.
The head of 3.0.1 is 2023-09-15_12-58_4b85906e5b91.
The head of 3.1.0 is 2023-12-01_12-03_b7851ee5522f.
But if I were to take a look at 2023-07-12_20-34_e0f6f91c2055 I see it was
introduced in 3.1.0 which would mean anyone coming from 2.1.3 has to go
straight to 3.1.0 otherwise you would not apply those two versions to your
database.
I only noticed this because we use tagging in our setup, or rather wanting
to use it more, and when trying to manage tags I got that error. My guess is
maybe that feature flag isn't being used by many while in development so the
error isn't very common.
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
