MVanDerlofske opened a new issue, #31459: URL: https://github.com/apache/superset/issues/31459
### Bug description When using the Docker Image tagged 4.1.1 it appears to be missing the ability to support MySQL as a datasource (among others). Reproduce (performed on both my local system and a newly setup test system): 1. export TAG=4.1.1 2. docker compose -f docker-compose-image-tag.yml up 3. resolve dependency issues that arise (reported in other bug tickets) Open the Superset interface and add a new database connection. You will note that the MySQL and Presto options are missing. ### Screenshots/recordings Screenshot of Add Database window on 4.1.1 tag:  Screenshot of editing an existing MySQL connection from an upgraded system:  Screenshot of expected add database window (taken for latest-dev 2024-12-14):  Screenshot of edit database connection window (taken for latest-dev 2024-12-14):  ### Superset version 4.1.1 ### Python version I don't know ### Node version I don't know ### Browser Chrome ### Additional context Error callstack: 2024-12-14 16:11:45,537:warning:superset.views.error_handling:SupersetErrorsException Traceback (most recent call last): File "/usr/local/lib/python3.10/site-packages/flask/app.py", line 1484, in full_dispatch_request rv = self.dispatch_request() File "/usr/local/lib/python3.10/site-packages/flask/app.py", line 1469, in dispatch_request return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args) File "/usr/local/lib/python3.10/site-packages/flask_appbuilder/security/decorators.py", line 95, in wraps return f(self, *args, **kwargs) File "/app/superset/views/base_api.py", line 119, in wraps duration, response = time_function(f, self, *args, **kwargs) File "/app/superset/utils/core.py", line 1364, in time_function response = func(*args, **kwargs) File "/app/superset/views/base_api.py", line 91, in wraps return f(self, *args, **kwargs) File "/app/superset/utils/log.py", line 303, in wrapper value = f(*args, **kwargs) File "/app/superset/sqllab/api.py", line 409, in execute_sql_query command_result: CommandResult = command.run() File "/app/superset/utils/decorators.py", line 266, in wrapped return on_error(ex) File "/app/superset/utils/decorators.py", line 236, in on_error raise ex File "/app/superset/utils/decorators.py", line 259, in wrapped result = func(*args, **kwargs) File "/app/superset/commands/sql_lab/execute.py", line 105, in run status = self._run_sql_json_exec_from_scratch() File "/app/superset/commands/sql_lab/execute.py", line 158, in _run_sql_json_exec_from_scratch return self._sql_json_executor.execute( File "/app/superset/sqllab/sql_json_executer.py", line 111, in execute raise SupersetErrorsException( superset.exceptions.SupersetErrorsException: [SupersetError(message="No module named 'MySQLdb'", error_type=<SupersetErrorType.GENERIC_DB_ENGINE_ERROR: 'GENERIC_DB_ENGINE_ERROR'>, level=<ErrorLevel.ERROR: 'error'>, extra={'engine_name': 'MySQL', 'issue_codes': [{'code': 1002, 'message': 'Issue 1002 - The database returned an unexpected error.'}]})] ### Checklist - [X] I have searched Superset docs and Slack and didn't find a solution to my problem. - [X] I have searched the GitHub issue tracker and didn't find a similar bug report. - [X] 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
