Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

DB password special character bug

See original GitHub issue

When a special character ‘@’ exists in the sqlalchemy URI it is not store correctly in superset metastore.

example URI: postgresql://<user>:123@456@<hostname>:5432/<db>

Expected results

escape the special character correctly after saving the Database entry

Actual results

what actually happens.

Screenshots

If applicable, add screenshots to help explain your problem.

How to reproduce the bug

Go to Sources -> Datasources -> Create New
Construct the URI and make sure the password has ‘@’ character.
Test Connection (Success)
Save Datasource
Open the newly created datasource
Test Connection (Failed)

In this stage if you replace the password part (‘XXXXXXXXXX’) in the URI with the actual password its working correctly

Environment

superset version: 0.37.0rc1

Issue Analytics

State:
Created 3 years ago
Comments:14 (5 by maintainers)

Top GitHub Comments

3reactions

mistercrunchcommented, Aug 7, 2020

Side note: I had a recent conversation with one of our designers and he mentioned the idea of moving away from URIs and having a more complete form with different fields for each component of the URI. Maybe an “advanced” option let’s you use the URI if you prefer. Then the UI would quote things for you.

2reactions

kaykumarcommented, Nov 16, 2021

I was able to make it work via replacing the special character with url encode value.

example: “pass@word” should be changed to “pass%40word” in SQLALCHEMY URI* field.