-
Notifications
You must be signed in to change notification settings - Fork 13.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exported MySQL Database Connection cannot be imported #30585
Comments
The issue with importing a MySQL connection that includes timeouts might be related to validation checks on the To resolve this, you can:
The workaround you've used is effective, but it might be worth investigating if there are any updates or configuration changes that could permanently resolve the issue. |
Bug description
Importing MySQL connection exported on different Superset instance fails on validation.
Expected result: Superset asks for user DB password and imports the connection
Actual results: Import error is shown in the "Connect a database" dialog
Workaround:
Extract the connection yaml file from the exported zip file and comment out the timeouts. Repack the zip file and import it.
Original MySQL.yaml:
Fixed MySQL.yaml:
Possibly related issues:
Screenshots/recordings
No response
Superset version
4.0.2
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: