-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Updated UC Model Registry Client to include aliases in RegisteredModel and ModelVersion payloads #8377
Conversation
…l and ModelVersion payloads Signed-off-by: Arpit Jasapara <arpit.jasapara@databricks.com>
Documentation preview for 4d1c5dc will be available here when this CircleCI job completes successfully. More info
|
Co-authored-by: Siddharth Murching <smurching@gmail.com> Signed-off-by: Arpit Jasapara <87999496+arpitjasa-db@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding the proto conversion tests! Basically LGTM, just had small comments
Signed-off-by: Arpit Jasapara <arpit.jasapara@databricks.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Signed-off-by: Arpit Jasapara <arpit.jasapara@databricks.com>
Related Issues/PRs
#8001
#8055
#8094
#8164
What changes are proposed in this pull request?
This PR adds aliases as a field on the RegisteredModel and ModelVersion payloads for the UC Model Registry, while modifying the respective conversion functions.
How is this patch tested?
Does this PR change the documentation?
Release Notes
Is this a user-facing change?
This PR adds aliases as a field on the RegisteredModel and ModelVersion payloads for the UC Model Registry, while modifying the respective conversion functions.
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/artifacts
: Artifact stores and artifact loggingarea/build
: Build and test infrastructure for MLflowarea/docs
: MLflow documentation pagesarea/examples
: Example codearea/model-registry
: Model Registry service, APIs, and the fluent client calls for Model Registryarea/models
: MLmodel format, model serialization/deserialization, flavorsarea/recipes
: Recipes, Recipe APIs, Recipe configs, Recipe Templatesarea/projects
: MLproject format, project running backendsarea/scoring
: MLflow Model server, model deployment tools, Spark UDFsarea/server-infra
: MLflow Tracking server backendarea/tracking
: Tracking Service, tracking client APIs, autologgingInterface
area/uiux
: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/docker
: Docker use across MLflow's components, such as MLflow Projects and MLflow Modelsarea/sqlalchemy
: Use of SQLAlchemy in the Tracking Service or Model Registryarea/windows
: Windows supportLanguage
language/r
: R APIs and clientslanguage/java
: Java APIs and clientslanguage/new
: Proposals for new client languagesIntegrations
integrations/azure
: Azure and Azure ML integrationsintegrations/sagemaker
: SageMaker integrationsintegrations/databricks
: Databricks integrationsHow should the PR be classified in the release notes? Choose one:
rn/breaking-change
- The PR will be mentioned in the "Breaking Changes" sectionrn/none
- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/feature
- A new user-facing feature worth mentioning in the release notesrn/bug-fix
- A user-facing bug fix worth mentioning in the release notesrn/documentation
- A user-facing documentation change worth mentioning in the release notes