Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable integration with the mlflow registry #260

Closed
Galileo-Galilei opened this issue Nov 7, 2021 · 0 comments · Fixed by #374
Closed

Enable integration with the mlflow registry #260

Galileo-Galilei opened this issue Nov 7, 2021 · 0 comments · Fixed by #374
Assignees
Labels
enhancement New feature or request

Comments

@Galileo-Galilei
Copy link
Owner

Galileo-Galilei commented Nov 7, 2021

Description

This is a catch-all ticket for model registry integration. Some ideas:

  • Add a key in mlflow.yml to set mlflow_registry_uri
  • Create a dataset which is able to save/load a specific version of a model in the registry uri
  • Add the possibility to create a new version of the same model instead of a new run when running e PipelineML with pipeline_ml_factory

Context

The model registry is becoming more and more prevalent while deploying in production and there is currently o support for this mlflow feature.

Possible Implementation

TBD

@Galileo-Galilei Galileo-Galilei self-assigned this Nov 7, 2021
@Galileo-Galilei Galileo-Galilei added enhancement New feature or request need-design-decision Several ways of implementation are possible and one must be chosen labels Nov 7, 2021
@Galileo-Galilei Galileo-Galilei added this to To do in Ongoing development via automation Nov 7, 2021
@Galileo-Galilei Galileo-Galilei moved this from To do to Planned for next release in Ongoing development Feb 13, 2022
@Galileo-Galilei Galileo-Galilei moved this from Planned for next release to To do in Ongoing development Mar 2, 2022
@Galileo-Galilei Galileo-Galilei moved this from Need design decision to Ready to develop in Ongoing development Mar 2, 2022
@Galileo-Galilei Galileo-Galilei removed the need-design-decision Several ways of implementation are possible and one must be chosen label Mar 2, 2022
Galileo-Galilei added a commit that referenced this issue Nov 27, 2022
Galileo-Galilei added a commit that referenced this issue Jan 15, 2023
@Galileo-Galilei Galileo-Galilei moved this from TODO - Ready to develop to Planned for next release in Ongoing development Jan 15, 2023
Ongoing development automation moved this from Planned for next release to Done Jan 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

Successfully merging a pull request may close this issue.

1 participant