-
Notifications
You must be signed in to change notification settings - Fork 34
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
Labels
enhancement
New feature or request
Comments
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
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
Oct 9, 2022
6 tasks
Galileo-Galilei
added a commit
that referenced
this issue
Oct 9, 2022
Galileo-Galilei
added a commit
that referenced
this issue
Oct 13, 2022
Galileo-Galilei
added a commit
that referenced
this issue
Oct 13, 2022
Galileo-Galilei
added a commit
that referenced
this issue
Nov 27, 2022
… mlflow model registry (#260)
6 tasks
Galileo-Galilei
added a commit
that referenced
this issue
Jan 15, 2023
… mlflow model registry (#260)
Galileo-Galilei
added a commit
that referenced
this issue
Jan 16, 2023
Galileo-Galilei
added a commit
that referenced
this issue
Jan 18, 2023
Galileo-Galilei
added a commit
that referenced
this issue
Jan 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
This is a catch-all ticket for model registry integration. Some ideas:
mlflow_registry_uri
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
The text was updated successfully, but these errors were encountered: