You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To manually evaluate some outputs of a run in the Evaluation tab in the MLflow UI, you need to log data using the mlflow.log_table method, which is not currently supported by any of the Dataset implementations in kedro-mlflow.
Context
I wanted to be able to view the table I created in one of the nodes in the Evaluation tab to compare it with other runs.
I've tried logging JSON as an artifact using MlflowArtifactDataset and pandas.JSONDataset with orient: "split" (since this is the same format MLflow uses when logging artifacts with mlflow.log_table).
As a workaround, I manually call mlflow.log_table from inside the node at the end of execution, but I am not sure if this is reliable and will always log data to the correct run, as I was unable to retrieve the run_id of the current run from inside the node.
Possible Implementation
Probably additional Dataset that will use mlflow.log_table instead of mlflow.log_artifact
Possible Alternatives
Manual logging but this is probably not very reliable
The text was updated successfully, but these errors were encountered:
Description
To manually evaluate some outputs of a run in the
Evaluation
tab in the MLflow UI, you need to log data using themlflow.log_table
method, which is not currently supported by any of theDataset
implementations inkedro-mlflow
.Context
I wanted to be able to view the table I created in one of the nodes in the
Evaluation
tab to compare it with other runs.I've tried logging JSON as an artifact using
MlflowArtifactDataset
andpandas.JSONDataset
withorient: "split"
(since this is the same format MLflow uses when logging artifacts withmlflow.log_table
).As a workaround, I manually call
mlflow.log_table
from inside the node at the end of execution, but I am not sure if this is reliable and will always log data to the correct run, as I was unable to retrieve therun_id
of the current run from inside the node.Possible Implementation
Probably additional Dataset that will use
mlflow.log_table
instead ofmlflow.log_artifact
Possible Alternatives
Manual logging but this is probably not very reliable
The text was updated successfully, but these errors were encountered: