MLFlow allow using other supported database backends as external database about charts HOT 3 OPEN

@carrodher I understand that my PR #25965 only exposes the configuration options regarding the used database engine and that container image does also need additional python libraries to support those other database engines.

I was about to push another PR to also extend the container image (https://github.com/bitnami/containers/blob/main/bitnami/mlflow/2/debian-12/Dockerfile) with e.g.

pymssql
pymysql
pyodbc
...

like mlFlow does intend to do for their own container image (https://github.com/mlflow/mlflow/pull/11669/files).

But apparently the Python libraries are already part of the COMPONENTS and packaged into the tar.gz files fetched from Stacksmith (https://github.com/bitnami/containers/blob/913d85fcaf8b8e7a7a719a6a0bb5bd2aff179928/bitnami/mlflow/2/debian-12/Dockerfile#L32C8-L32C14)

Is there some sort of build script or requirements script that I can extend to have the required Python libraries added or is that something you would need to do?

from charts.

Thank you for opening this issue and submitting the associated Pull Request. Our team will review and provide feedback. Once the PR is merged, the issue will automatically close.

Regarding the python version, yes, it is something handled internally by our automated test & release pipeline. If changing that version is required, feel free to comment it in the container's PR so the reviewer can test that change internally.

Your contribution is greatly appreciated!

from charts.

@frittentheke - we discuss this in #22992 though specifically that is requesting mysql access.

Edit: I am thinking possibly https://github.com/mlflow/mlflow/pull/11669/files is a result of my request in that issue.

from charts.