mistercrunch commented on issue #31459: URL: https://github.com/apache/superset/issues/31459#issuecomment-2675456046
As convenient as it may be to include database drivers into the `lean` images, I still stand by the decision of NOT bundling them in. Every single deploy needs its own set of driver (whether is mysql/postgres/oracle/mssql for metadata db) and different set of analytics database. Serving a `fat` image might be nice, but I would not recommend friends / anyone to use such an image, and it'd be a huge pain to maintain. The reality is that if you want to run Superset in production, you should extend `lean` with the set of drivers you need for your environment, and at that point you're in the business of picking the right drivers and keeping them up to date. Note that we try and maintain the "extra_requires" as metadata of supported drivers/versions, but it's been a bit of a loosing battle given the state of the ecosystem. Knowing this, would love help to improve the docs to make this as clear/straightforward as possible. -- 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]
