Clarify mlflow gc command behavior for pinned runs and registered models#18704
Merged
Clarify mlflow gc command behavior for pinned runs and registered models#18704
Conversation
Contributor
|
@Copilot Thank you for the contribution! Could you fix the following issue(s)? ⚠ Invalid PR templateThis PR does not appear to have been filed using the MLflow PR template. Please copy the PR template from here and fill it out. |
Add clarification to the gc command docstring about what factors are NOT considered when determining which runs to delete: - Pinned runs (UI-only feature) - Registered models - Tags or other metadata Also update the --older-than help text to clarify it filters based on when runs were moved to the deleted lifecycle stage, not their creation time. Co-authored-by: harupy <17039389+harupy@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Clarify mlflow gc handling of pinned runs
Clarify mlflow gc command behavior for pinned runs and registered models
Nov 6, 2025
harupy
reviewed
Nov 6, 2025
🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
Contributor
|
Documentation preview for 481566f is available at: More info
|
harupy
reviewed
Nov 7, 2025
Co-authored-by: harupy <17039389+harupy@users.noreply.github.com>
harupy
reviewed
Nov 7, 2025
| .. note:: | ||
|
|
||
| This command only considers lifecycle stage and the specified deletion criteria. | ||
| It does **not** check for pinned runs, registered models, or tags. Pinning is a |
Member
There was a problem hiding this comment.
not sure if we need to mention pinned runs but it doesn't hurt anyone.
harupy
reviewed
Nov 7, 2025
Signed-off-by: Harutaka Kawamura <hkawamura0130@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related Issues/PRs
Resolve #14637
What changes are proposed in this pull request?
The
mlflow gccommand documentation did not clarify whether pinned runs or runs with registered models are protected from deletion. This caused confusion when using--older-thanto preserve recent runs while potentially wanting to retain important older runs.Changes:
.. note::section togccommand docstring documenting what is NOT considered:--older-thanfilters by deletion time (when moved todeletedlifecycle stage), not creation timedeletedlifecycle stage before gc can remove themHow is this PR tested?
Verified existing gc tests pass:
test_mlflow_gc_sqlite,test_mlflow_gc_sqlite_older_than,test_mlflow_gc_file_storeDoes this PR require documentation update?
Release Notes
Is this a user-facing change?
Documentation now clarifies that
mlflow gcoperates solely on lifecycle stage and specified criteria (--older-than,--run-ids,--experiment-ids). Pinned runs, registered models, and metadata do not prevent deletion.What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/tracking: Tracking Service, tracking client APIs, autologgingarea/models: MLmodel format, model serialization/deserialization, flavorsarea/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registryarea/scoring: MLflow Model server, model deployment tools, Spark UDFsarea/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflowsarea/gateway: MLflow AI Gateway client APIs, server, and third-party integrationsarea/prompts: MLflow prompt engineering features, prompt templates, and prompt managementarea/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionalityarea/projects: MLproject format, project running backendsarea/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/build: Build and test infrastructure for MLflowarea/docs: MLflow documentation pagesHow 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?
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.