worker24h opened a new issue, #31887: URL: https://github.com/apache/superset/issues/31887
### Bug description ```bash root@superset-588675d6f7-52vtb:/app# root@superset-588675d6f7-52vtb:/app# superset db upgrade 2025-01-16 15:57:24,377:DEBUG:superset.utils.logging_configurator:logging was configured successfully 2025-01-16 15:57:24,381:DEBUG:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'> /usr/local/lib/python3.10/site-packages/flask_limiter/extension.py:333: UserWarning: Using the in-memory storage for tracking rate limits as no storage was explicitly specified. This is not recommended for production use. See: https://flask-limiter.readthedocs.io#configuring-a-storage-backend for documentation about configuring the storage backend. warnings.warn( 2025-01-16 15:57:24,461:INFO:superset.utils.screenshots:No PIL installation found 2025-01-16 15:57:24,749:INFO:superset.utils.pdf:No PIL installation found WARNI [alembic.env] SQLite Database support for metadata databases will be removed in a future version of Superset. INFO [alembic.env] Starting the migration scripts. INFO [alembic.runtime.migration] Context impl SQLiteImpl. INFO [alembic.runtime.migration] Will assume transactional DDL. INFO [alembic.env] Migration scripts completed. Duration: 00:00:00 root@superset-588675d6f7-52vtb:/app# ``` 1. I used MYSQL to store metadata，not sqlite 2. The upgrade command executed success， but the table hasn't changed ### Screenshots/recordings _No response_ ### Superset version 4.1.1 ### Python version 3.10 ### Node version 18 or greater ### Browser Chrome ### Additional context _No response_ ### Checklist - [ ] I have searched Superset docs and Slack and didn't find a solution to my problem. - [ ] I have searched the GitHub issue tracker and didn't find a similar bug report. - [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section. -- 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.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
