NiklasRosenstein commented on issue #35174:
URL: https://github.com/apache/superset/issues/35174#issuecomment-3485506079

   I'm also running into this issue. And to @rusackas point, I've run into it 
before two years ago already: https://github.com/apache/superset/issues/23577 
(note how I had to install `psycopg2` in the `bootstrapScript`).
   
   I get this error not when connecting to an external database. It seems 
reasonable to require installing additional drivers in some way explicitly for 
various reasons (e.g. license, image bloat, maintenance, etc.)
   
   The error appears with a pretty vanilla installation of the superset Helm 
chart when it tries to connect to _it's own Postgres DB_. We're looking to 
evaluate Superset against other (some not open source) competitors in the 
space, but this doesn't exactly inspire confidence in the project unfortunately.
   
   ```yaml
   # helmfile.yaml
   repositories:
     - name: superset
       url: https://apache.github.io/superset
   
   releases:
   - name: superset
     namespace: superset
     chart: superset/superset
     version: "0.15.0"
     values:
       # Bitnami has moved their container images behind a paywall. The 
Superset Helm charts have not been updated yet.
       # See 
https://github.com/apache/superset/issues/34414#issuecomment-3307806333
       - postgresql:
           image:
             repository: bitnamilegacy/postgresql
         redis:
           image:
             repository: bitnamilegacy/redis
       - configOverrides:
           secret: |
             SECRET_KEY = 'CHANGE_ME_TO_A_SECRET'
   ```


-- 
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