[Workspace] Add REST store and fluent workspace APIs#19449
Merged
B-Step62 merged 4 commits intomlflow:orgnization-supportfrom Dec 20, 2025
Merged
[Workspace] Add REST store and fluent workspace APIs#19449B-Step62 merged 4 commits intomlflow:orgnization-supportfrom
B-Step62 merged 4 commits intomlflow:orgnization-supportfrom
Conversation
Tracking and model registry REST stores now detect if the server has workspaces enabled if a user specifies a workspace. When a workspace is set and the servers support it, the REST store passes an X-MLFLOW-WORKSPACE header to the HTTP request. Signed-off-by: mprahl <mprahl@users.noreply.github.com>
Signed-off-by: mprahl <mprahl@users.noreply.github.com>
Collaborator
Author
|
/cc @B-Step62 @BenWilson2 |
Signed-off-by: mprahl <mprahl@users.noreply.github.com>
B-Step62
reviewed
Dec 18, 2025
Collaborator
B-Step62
left a comment
There was a problem hiding this comment.
Overall looks good, left a few small comments
mlflow/server/handlers.py
Outdated
| _verify_model_registry_store_workspace_support(registry_store) | ||
|
|
||
|
|
||
| def _store_supports_workspaces(store: object) -> bool: |
Collaborator
There was a problem hiding this comment.
Suggested change
| def _store_supports_workspaces(store: object) -> bool: | |
| def _store_supports_workspaces(store: AbstractStore) -> bool: |
| self._workspace_support = supported | ||
| return supported | ||
|
|
||
| def _enforce_workspace_support(self) -> None: |
Collaborator
There was a problem hiding this comment.
Suggested change
| def _enforce_workspace_support(self) -> None: | |
| def _validate_workspace_support_if_specified(self) -> None: |
nit: enforce sounds like it has some side effect.
mlflow/tracking/_workspace/fluent.py
Outdated
| raise | ||
|
|
||
|
|
||
| @experimental(version="3.8.0") |
Collaborator
There was a problem hiding this comment.
Suggested change
| @experimental(version="3.8.0") | |
| @experimental(version="3.9.0") |
3.8.0 was just cut last week
mlflow/tracking/_workspace/fluent.py
Outdated
| if exc.error_code == databricks_pb2.ErrorCode.Name(databricks_pb2.ENDPOINT_NOT_FOUND): | ||
| raise MlflowException( | ||
| "The configured tracking server does not expose workspace APIs. " | ||
| "Ensure multi-tenancy is enabled.", |
Collaborator
There was a problem hiding this comment.
Suggested change
| "Ensure multi-tenancy is enabled.", | |
| "Ensure workspace is enabled.", |
Let's avoid the term 'multi-tenancy' as discussed offline.
B-Step62
approved these changes
Dec 18, 2025
Contributor
|
Documentation preview for 53875b5 is available at: More info
|
Signed-off-by: mprahl <mprahl@users.noreply.github.com>
mprahl
added a commit
to mprahl/mlflow
that referenced
this pull request
Jan 16, 2026
Signed-off-by: mprahl <mprahl@users.noreply.github.com>
B-Step62
pushed a commit
to B-Step62/mlflow
that referenced
this pull request
Jan 19, 2026
Signed-off-by: mprahl <mprahl@users.noreply.github.com>
B-Step62
pushed a commit
to B-Step62/mlflow
that referenced
this pull request
Feb 3, 2026
Signed-off-by: mprahl <mprahl@users.noreply.github.com>
mprahl
added a commit
to mprahl/mlflow
that referenced
this pull request
Feb 3, 2026
Signed-off-by: mprahl <mprahl@users.noreply.github.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.
🛠 DevTools 🛠
Install mlflow from this PR
For Databricks, use the following command:
Related Issues/PRs
#1464
#5844
Design document: https://docs.google.com/document/d/1IbFfceCmWV3knJfc0ninn58EXLVbHUh1meV_pknOM40/edit
What changes are proposed in this pull request?
This adds workspace support to the tracking and model registry REST stores. It also adds the workspace related fluent APIs, and addresses some of the optional feedback from #19319.
How is this PR tested?
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
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?
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?
Bug fixes, doc updates and new features usually go into minor releases.
Bug fixes and doc updates usually go into patch releases.