refactor: Migrate Azure ML logging to MLFlow and SDK V2#78
refactor: Migrate Azure ML logging to MLFlow and SDK V2#78isma-dev wants to merge 3 commits intomicrosoft:mainfrom
Conversation
|
@isma-dev please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
|
Hi @kmaziarz, I'm Ismael, from GenChem project, NVS. We are actively migrating our projects to use the latest Azure ML SDK V2. This pull request updates the logging functionality within moler to align with the new standard. The current implementation uses the deprecated SDK V1. This change migrates the logging to the V2 approach, utilizing MLFlow as the recommended method. I've updated the relevant code and dependencies to support this change. You can find more information about this migration path in the official Microsoft documentation. Let me know if you have any questions or require further details. Regards, |
The current implementation for logging metrics in Azure ML uses the deprecated SDK V1. This pull request migrates the logging functionality to the recommended SDK V2 approach, which suggests using the MLFlow component. There is no direct migration path from the old Run object's logging methods, so this change replaces them with mlflow functions.
This update also includes the necessary dependency changes to support MLFlow.
For more information on the migration, please see the official Microsoft documentation.