09-26-2021 11:34 PM
Would it be possible to somehow save the data, metrics of all experiments captured by self-managed mlflow using A/mazon RDS, S3 as backend and then load it to databricks managed mlflow and make it available in the UI? This is required as a part of migration activity.
05-20-2022 03:31 AM
@Kaniz Fatma : Hi Fatima,
mlflow-export-import is still not a recommended solution and has no support from Databricks. This is clarified by Databricks SA's themselves.
I have developed an another approach where I am capturing the statistics of a particular run which is needed to be migrated to higher env. (like pre-prod or prod) and then creating a mlflow run with those statistics instead of re-running the entire huge model. This is working perfectly and is within the logical support of Databricks.
09-28-2021 12:49 AM
Hi @Maverick! My name is Kaniz, and I'm the technical moderator here. Great to meet you, and thanks for your question! Let's see if your peers on the community have an answer to your question first. Or else I will follow up with my team and get back to you soon.Thanks.
10-05-2021 11:27 AM
You can migrate your MLflow experiment and runs using the MLflow API with this toolkit: https://github.com/amesar/mlflow-export-import
03-07-2022 05:06 AM
@Andre Mesarovic : Is this solution, Databricks approved for enterprise usage?
I believe this is not an approved solution and also I can see many issues in it while doing import and export like nested metrics are not imported correctly etc.
03-07-2022 08:08 AM
mlflow-export-import is an open source tool used by both OSS and Databricks users. It is in the process of being a recommended solution for Databricks MLflow migrations. Create a ticket for any issues at: https://github.com/amesar/mlflow-export-import/issues
05-18-2022 01:40 PM
Hi @Saurabh Verma , Just a friendly follow-up. Do you still need help or the above responses help you to find the solution? Please let us know.
05-20-2022 03:31 AM
@Kaniz Fatma : Hi Fatima,
mlflow-export-import is still not a recommended solution and has no support from Databricks. This is clarified by Databricks SA's themselves.
I have developed an another approach where I am capturing the statistics of a particular run which is needed to be migrated to higher env. (like pre-prod or prod) and then creating a mlflow run with those statistics instead of re-running the entire huge model. This is working perfectly and is within the logical support of Databricks.
05-20-2022 03:35 AM
Hi @Saurabh Verma , I'm glad that you have got a solution to your question. Would you like to mark your answer as the best?
05-20-2022 08:55 AM
Hi @Saurabh Verma , mlflow-export-import is in the process of being the Databricks recommended solution. We will have it in our official DB docs soon. It is based on the open source MLflow API and works for both OSS and DB. We have over 105 customers using it. It is the only way to migrate MLflow objects from one tracking server (workspace) to another.
Join our fast-growing data practitioner and expert community of 80K+ members, ready to discover, help and collaborate together while making meaningful connections.
Click here to register and join today!
Engage in exciting technical discussions, join a group with your peers and meet our Featured Members.