You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When connecting a DB connection to Superset, it's possible to specify the DB version (this is used for a few DB Engines). If filled, the version field is included in the export file, however the import is not configured to handle it, and therefore the import fails.
How to reproduce the bug
Create a DB connection or modify an existing one.
Navigate to the ADVANCED tab, and expand the Other section.
Set any value in the VERSION field.
Save changes.
Export the DB connection.
Try to import it.
Expected results
The import should work properly.
Actual results
The import doesn't work.
Environment
browser type and version: Chrome version 119.0.6045.159
superset version: 0.0.0-dev (running master)
python version: 3.9.0
node.js version: v16.14.2
any feature flags active: not relevant to reproduce the issue
Checklist
Make sure to follow these steps before submitting your issue - thank you!
I have checked the superset logs for python stacktraces and included it here as text if there are any.
I have reproduced the issue with at least the latest released version of superset.
I have checked the issue tracker for the same issue and I haven't found one similar.
The text was updated successfully, but these errors were encountered:
When connecting a DB connection to Superset, it's possible to specify the DB version (this is used for a few DB Engines). If filled, the version field is included in the export file, however the import is not configured to handle it, and therefore the import fails.
How to reproduce the bug
Expected results
The import should work properly.
Actual results
The import doesn't work.
Environment
119.0.6045.159
0.0.0-dev
(running master)3.9.0
v16.14.2
Checklist
Make sure to follow these steps before submitting your issue - thank you!
The text was updated successfully, but these errors were encountered: