The kedro-mlflow version used to create a KedroPipelineModel should be enforced #104
Labels
enhancement
New feature or request
need-design-decision
Several ways of implementation are possible and one must be chosen
Description
The
KedroPipelineModel
API is not stable yet and slightly evolves between releases. I suggest that we store the kedro-mlflow version used to create the class when logging it.Context
The API breaking changes may prevent users to load a model from mlflow if they do not have the same version as the one used to save it. If the
environment.yml
is not restrictive enough, some users may experience someKedroPipelineModel
errors which are not informative on the problem. This especially happens when a model is loaded interactively (when the model is packaged with theenvironment.yml
, the version is supposed to be pinned.Possible Implementation
Add an attribute to
KedroPipelineModel
with thekedro-mlflow
used for creating the model.Possible Alternatives
Do not specify it, and assume user will properly fill the environment.yml file and eventually notice the conflict.
The text was updated successfully, but these errors were encountered: