-
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
Add start run by name #11896
base: master
Are you sure you want to change the base?
Add start run by name #11896
Conversation
@m-blasiak 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. |
15a8b74
to
a7542f1
Compare
Signed-off-by: m-blasiak <37832014+m-blasiak@users.noreply.github.com>
Signed-off-by: m-blasiak <37832014+m-blasiak@users.noreply.github.com>
Signed-off-by: m-blasiak <37832014+m-blasiak@users.noreply.github.com>
Signed-off-by: m-blasiak <37832014+m-blasiak@users.noreply.github.com>
daa427f
to
a1d4edd
Compare
Signed-off-by: m-blasiak <37832014+m-blasiak@users.noreply.github.com>
a1d4edd
to
0bfa6c6
Compare
Documentation preview for ec563f3 will be available when this CircleCI job More info
|
@harupy what do you think about this? it looks fine to me (after lint errors are fixed). it's basically to add a convenience function to allow resuming a run by name (see discussion in #11783, the |
Signed-off-by: m-blasiak <37832014+m-blasiak@users.noreply.github.com>
Signed-off-by: m-blasiak <37832014+m-blasiak@users.noreply.github.com>
@daniellok-db @harupy Any chance to get it reviewed soon? The lint errors should be fixed now |
After some discussion, the team decided that since this function serves a fairly specific purpose, it's better if this is kept as user code, rather than being included in the library. Sorry for the delays on this! |
🛠 DevTools 🛠
Install mlflow from this PR
Checkout with GitHub CLI
Related Issues/PRs
Resolve #11783
What changes are proposed in this pull request?
Creates new function to start an mlflow run
start_run_by_name
.Similarly to
start_run
this will attempt to resume a run (by performing an exact name lookup), if no runs exist with the specified name, a new run will be created.In case lookup returns multiple runs with the specified name, an exception is raised
How is this PR tested?
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
Adds
start_run_by_name
function to make it easier to resume existing runs.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/deployments
: MLflow Deployments client APIs, server, and third-party Deployments integrationsarea/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/none
- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/breaking-change
- The PR will be mentioned in the "Breaking Changes" 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 notesShould this PR be included in the next patch release?
Yes
should be selected for bug fixes, documentation updates, and other small changes.No
should be selected for new features and larger changes. If you're unsure about the release classification of this PR, leave this unchecked to let the maintainers decide.What is a minor/patch release?
Bug fixes, doc updates and new features usually go into minor releases.
Bug fixes and doc updates usually go into patch releases.