-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Update parse model URI to prevent breaking old cases while supporting aliases #8322
Conversation
Documentation preview for 17053c8 will be available here when this CircleCI job completes successfully. More info
|
@arpitjasa-db Thank you for the contribution! Could you fix the following issue(s)? ⚠ DCO checkThe DCO check failed. Please sign off your commit(s) by following the instructions here. See https://github.com/mlflow/mlflow/blob/master/CONTRIBUTING.md#sign-your-work for more details. |
… aliases Signed-off-by: Arpit Jasapara <arpit.jasapara@databricks.com>
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 once https://github.com/mlflow/mlflow/pull/8322/files#r1177120097 is addressed. Thanks @arpitjasa-db !
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.
Requesting changes until https://github.com/mlflow/mlflow/pull/8322/files#r1177158990 is addressed
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! Thanks @arpitjasa-db !
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! Great work @arpitjasa-db :)
Signed-off-by: Arpit Jasapara <arpit.jasapara@databricks.com>
… aliases (mlflow#8322) * Update parse model URI to prevent breaking old cases while supporting aliases Signed-off-by: Arpit Jasapara <arpit.jasapara@databricks.com> * Applied comments Signed-off-by: Arpit Jasapara <arpit.jasapara@databricks.com> * Addressed comments Signed-off-by: Arpit Jasapara <arpit.jasapara@databricks.com> * Allow fragments false Signed-off-by: Arpit Jasapara <arpit.jasapara@databricks.com> --------- Signed-off-by: Arpit Jasapara <arpit.jasapara@databricks.com> Signed-off-by: Larry O’Brien <larry.obrien@databricks.com>
Related Issues/PRs
#8164
What changes are proposed in this pull request?
This PR fixes model naming and other URI regressions caused by #8164, while still maintaining the aliases logic.
How is this patch tested?
Does this PR change the documentation?
Release Notes
Is this a user-facing change?
(Details in 1-2 sentences. You can just refer to another PR with a description if this PR is part of a larger change.)
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