Open dragosmc opened 1 year ago
Hi @dragosmc, thanks for flagging this! This is actually a known issue that we've seen on our side as well, and we're going to work on fixing it in the future.
For now, to unblock yourself, are you able to downgrade MLFlow to 1.30.0? This should work - let me know if it does
I can give a hand to fixing this also.
@dragosmc If you want to take a stab at fixing this in Ludwig, that would be amazing
Hi @dragosmc, thanks for flagging this! This is actually a known issue that we've seen on our side as well, and we're going to work on fixing it in the future.
For now, to unblock yourself, are you able to downgrade MLFlow to 1.30.0? This should work - let me know if it does
Unfortunatelly I can't downgrade to 1.30, but I'd be happy to help fixing this -I'll have a look through the code and come up witha PR fairly soon.
Thanks.
Thanks @dragosmc! All the relevant code should be contained in https://github.com/ludwig-ai/ludwig/blob/master/ludwig/contribs/mlflow/__init__.py#L38
I had a go at this and after my digging I believe the problem lies with MLflow. From what I can see the ludwig calls Model.log()
which then splits/deals with the data as it wishes.
Moreover, the error message is misleading since the exception is raised during the /2.0/mlflow/runs/log-model
call and not specifically creating a tag.
I will have to dig a bit more into MLflow itself to understand where exactly the json payload gets split into tags vs no-tags when logging it, but as it stands now I couldn't get this to work with 2.1.1 or 1.30.0.
Describe the bug I'm running ludwig 0.6.4 and mlflow 2.1.1 and I get a warning about ludwig being unable to log metadata due to some mlflow limitation.
To Reproduce
Expected behavior Metadata to be logged successfully into MLflow.
Screenshots
and traceback
Environment (please complete the following information):
Additional context The related issue which won't be fixed from MLflow's side https://github.com/mlflow/mlflow/issues/2892
I can give a hand to fixing this also.