Closed cariveroco closed 1 month ago
Indeed, thanks for raising this issue. I guess the right way is to use get_metric_history
which seems implemented in all stores: https://github.com/search?q=repo%3Amlflow%2Fmlflow+get_metric_history&type=code
Just faced the same issue; pinning mlflow version to earlier one doesn't work due to compatibility with py3.10
I'll try to take a look at it next week. This is a bug and it should be corrected quickly. Thank you for your patience.
Hi, @cariveroco @mck-star-yar can you test pip install git+https://github.com/Galileo-Galilei/kedro-mlflow.git@582-metrics_history-dataset-to-server
and tell me if it fixes the issue?
Hi @Galileo-Galilei, it's working now on my end. Thank you very much!
Description
Kedro pipeline run can't publish objects of type
kedro_mlflow.io.metrics.MlflowMetricsHistoryDataset
to a remote Mlflow tracking server.Context
A kedro pipeline that can successfully publish a
kedro_mlflow.io.metrics.MlflowMetricsHistoryDataset
to a local Mlflow tracking server, is throwing an error when trying to pulish to a remote server. Previously, the same pipeline can successfully publish the metrics to both local and remote servers when the metrics was still configured to be of typekedro_mlflow.io.metrics.MlflowMetricsDataSet
in kedro-mlflow v.0.11.10.Based on the errors thrown, this may be related to this bug, where the suspected cause is that the
get_all_metrics
method is implemented forFileStore
(local tracking server) but not forRestStore
(remote tracking server).Steps to Reproduce
kedro_mlflow.io.metrics.MlflowMetricsHistoryDataset
.mlflow.yml
file to a remote Mlflow tracking server.Expected Result
The pipeline execution is completed successfully, and objects configured to be of type
kedro_mlflow.io.metrics.MlflowMetricsHistoryDataset
are successfully published to the remote Mlflow tracking server.Actual Result
The pipeline execution is completed successfully, but the run still throws back an error and can't publish the
kedro_mlflow.io.metrics.MlflowMetricsHistoryDataset
to the remote Mlflow tracking server. The error does not happen when running the same code (on exactly the same environment) with a local tracking server.Your Environment
kedro
andkedro-mlflow
version used (pip show kedro
andpip show kedro-mlflow
): kedro 0.19.6 and kedro-mlflow 0.12.2 (mlflow 2.12.1)python -V
): 3.10.14Does the bug also happen with the last version on master?
The bug previously does not exist with the following setup:
kedro_mlflow.io.metrics.MlflowMetricsDataSet
)