Re: [I] sqlalchemy engine should be created once per process [superset]

["rusackas (via GitHub)" <gi...@apache.org>]

rusackas commented on issue #27897:
URL: https://github.com/apache/superset/issues/27897#issuecomment-3948567940

   Checking in on this one. The draft PR #27899 that proposed a fix was closed without merging in July 2025. The underlying issue still appears to be present - `_get_sqla_engine()` still calls `create_engine()` on every invocation.
   
   @betodealmeida's point about NullPool is an important consideration: since the current design uses NullPool (because engines were expected to be short-lived), moving to engine caching would require a strategy for connection pool configuration.
   
   @betodealmeida @villebro - is anyone actively working on this? If not, should we leave it open for the community to pick up, or close it as not-planned for now?


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org