L0x6 opened a new issue, #25501:
URL: https://github.com/apache/superset/issues/25501

   I am upgrading superset from version 2.0.1 to version 3.0.0 (same issue 
arises when tested with version 2.1.1)
   I m using helm chart 0.10.9 and postgresql is used as metadata database.
   When deploying with default passwords (specially the database password), 
everything works fine.
   But when i use a db password containing special character "@" (like 
p@ssword), deployment ends with error. 
   It s unable to connect to the database because it's treating the after "@" 
as the starting of the db hostname.
   
   The same password was used in version 2.0.1 and its working fine
   
   #### How to reproduce the bug
   
   1. using helm chart values file change the db password to something 
containing "@" like  p@ssword
   2. Make sure postgresql is enabled
   3. Deploy superset (helm install....)
   4. Kubectl get pod
   5. See error in all superset containers basically (except for postgresql and 
redis)
   
   ### Expected results
   
   Database creation and initialization successful, deployment running without 
errors
   
   ### Actual results
   Error at DB creation and initialization step
   ( i think Database connection string is not url encoding or escaping the 
special characters in the password)
   
   #### Screenshots
   
   If applicable, add screenshots to help explain your problem.
   
![tmp_39ddb507-9de9-49c3-b4bd-38747ee87e37](https://github.com/apache/superset/assets/45522559/17609cea-8f73-4825-aa55-ff3d1fb84b93)
   
   
   ### Environment
   
   - browser type and version: edge (not related i guess)
   - superset version: `3.0.0` and `2.1.1`
   - python version: `3.9`
   - node.js version: `default`
   
   ### Checklist
   
   Yes i did.
   
   - [ ] 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.
   
   ### Additional context
   
   I went through the commits related to sqlalchemy on superset and i think the 
problem started after upgrading from sqlalchemy 1.3 to 1.4,
   There was so many changes in database uri functions and how it's treating 
the uri before passing it to engine (postgresql in my case) #19890 


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to