Use SQLite as default unless existing mlruns data is detected#18497
Use SQLite as default unless existing mlruns data is detected#18497harupy merged 17 commits intomlflow:masterfrom
Conversation
|
Documentation preview for 34e5bc4 is available at: More info
|
4a7be95 to
98020fb
Compare
Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
e29e143 to
2e12c65
Compare
Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
| "See https://github.com/mlflow/mlflow/issues/18534 for feedback and how to migrate " | ||
| "existing data.", |
There was a problem hiding this comment.
Ideally we should add both. Can we add a notable warning box in https://mlflow.org/docs/latest/self-hosting/ about the defauilt change and link to Github issue for details? Can we do that in a follow-up? I think we need some doc clean up anyway (e.g., remove explicit '--backend-store-uri sqlite:///mlflow.db' specification in some examples)
|
/resolve ✅ Workflow completed successfully. Claude OutputSummaryI successfully resolved the unresolved PR review comments for PR #18497. Here's what was addressed: Changes Made:
Skipped:
Commit:All changes have been committed locally with DCO sign-off (commit: |
- Change deprecation warning from "is deprecated" to "will be deprecated" for softer tone - Add context to _has_existing_mlruns_data() docstring explaining backward compatibility purpose 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: mlflow-app[bot] <mlflow-app[bot]@users.noreply.github.com>
- Change deprecation warning from "is deprecated" to "will be deprecated" - Update terminology from "model registry backend" to "tracking backend" - Update tests to match the new warning message format - Improve warning text clarity by restructuring the migration guidance 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
Updates self-hosting documentation to reflect that SQLite is now the default tracking backend (changed in MLflow 3.7 via mlflow#18497). Changes: - Add warning box in self-hosting overview about default change - Update quickstart examples to remove explicit SQLite flags - Update tracking server documentation with new defaults - Add guidance for existing users (auto-detection) and new users Addresses: mlflow#18497 (comment) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
Updates self-hosting documentation to reflect that SQLite is now the default tracking backend (changed in MLflow 3.7 via mlflow#18497). Changes: - Add warning box in self-hosting overview about default change - Update quickstart examples to remove explicit SQLite flags - Update tracking server documentation with new defaults - Add guidance for existing users (auto-detection) and new users Addresses: mlflow#18497 (comment) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
Updates self-hosting documentation to reflect that SQLite is now the default tracking backend (changed in MLflow 3.7 via mlflow#18497). Changes: - Add warning box in self-hosting overview about default change - Update quickstart examples to remove explicit SQLite flags - Update tracking server documentation with new defaults - Add guidance for existing users (auto-detection) and new users Addresses: mlflow#18497 (comment) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
Updates self-hosting documentation to reflect that SQLite is now the default tracking backend (changed in MLflow 3.7 via mlflow#18497). Changes: - Add warning box in self-hosting overview about default change - Update quickstart examples to remove explicit SQLite flags - Update tracking server documentation with new defaults - Add guidance for existing users (auto-detection) and new users Addresses: mlflow#18497 (comment) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
Updates self-hosting documentation to reflect that SQLite is now the default tracking backend (changed in MLflow 3.7 via mlflow#18497). Changes: - Add warning box in self-hosting overview about default change - Update quickstart examples to remove explicit SQLite flags - Update tracking server documentation with new defaults - Add guidance for existing users (auto-detection) and new users Addresses: mlflow#18497 (comment) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
Updates self-hosting documentation to reflect that SQLite is now the default tracking backend (changed in MLflow 3.7 via mlflow#18497). Changes: - Add warning box in self-hosting overview about default change - Update quickstart examples to remove explicit SQLite flags - Update tracking server documentation with new defaults - Add guidance for existing users (auto-detection) and new users Addresses: mlflow#18497 (comment) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
…#18497) Signed-off-by: harupy <17039389+harupy@users.noreply.github.com> Signed-off-by: mlflow-app[bot] <mlflow-app[bot]@users.noreply.github.com> Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: mlflow-app[bot] <mlflow-app[bot]@users.noreply.github.com>
…#18497) Signed-off-by: harupy <17039389+harupy@users.noreply.github.com> Signed-off-by: mlflow-app[bot] <mlflow-app[bot]@users.noreply.github.com> Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: mlflow-app[bot] <mlflow-app[bot]@users.noreply.github.com>
…#18497) Signed-off-by: harupy <17039389+harupy@users.noreply.github.com> Signed-off-by: mlflow-app[bot] <mlflow-app[bot]@users.noreply.github.com> Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: mlflow-app[bot] <mlflow-app[bot]@users.noreply.github.com> Signed-off-by: Tian Lan <sky.blue266000@gmail.com>
Related Issues/PRs
#18534
What changes are proposed in this pull request?
This PR changes the default tracking URI from file-based storage (
./mlruns) to SQLite database (sqlite:///mlflow.db).Backward Compatibility: Existing
mlrunsdirectories with experiment data are automatically detected and continue using file store, ensuring seamless migration for existing users.How is this PR tested?
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
Breaking Change: The default tracking URI has been changed from file-based storage (
./mlruns) to SQLite database (sqlite:///mlflow.db). Users who rely on the default behavior will now use SQLite instead of file-based storage. To revert to the previous behavior, setMLFLOW_TRACKING_URI=./mlrunsor usemlflow.set_tracking_uri("./mlruns").What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/tracking: Tracking Service, tracking client APIs, autologgingarea/build: Build and test infrastructure for MLflowHow should the PR be classified in the release notes? Choose one:
rn/breaking-change- The PR will be mentioned in the "Breaking Changes" sectionShould this PR be included in the next patch release?
Yesshould be selected for bug fixes, documentation updates, and other small changes.Noshould 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?
Minor release: a release that increments the second part of the version number (e.g., 1.2.0 -> 1.3.0).
Bug fixes, doc updates and new features usually go into minor releases.
Patch release: a release that increments the third part of the version number (e.g., 1.2.0 -> 1.2.1).
Bug fixes and doc updates usually go into patch releases.
Yes (this PR will be cherry-picked and included in the next patch release)
No (this PR will be included in the next minor release)