Deprecate Unity Catalog function integration in AI Gateway#19457
Deprecate Unity Catalog function integration in AI Gateway#19457harupy merged 3 commits intomlflow:masterfrom
Conversation
Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
This PR deprecates the Unity Catalog function integration feature in the MLflow AI Gateway to prepare for its eventual removal.
Key Changes:
- Added runtime deprecation warning that emits a
FutureWarningwhenMLFLOW_ENABLE_UC_FUNCTIONSis enabled - Updated environment variable docstring to indicate the feature is deprecated
- Added deprecation notice at the top of the Unity Catalog integration documentation page
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| mlflow/gateway/providers/openai.py | Added warnings import and FutureWarning emission in the chat() method when UC functions are enabled |
| mlflow/environment_variables.py | Updated docstring for MLFLOW_ENABLE_UC_FUNCTIONS to indicate deprecation status |
| docs/docs/genai/governance/unity-catalog.mdx | Added prominent deprecation warning box at the top of the documentation page |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
/resolve ✅ Workflow completed successfully. Claude OutputPerfect! I've successfully addressed all unresolved PR review comments for PR #19457. Here's what was done: SummaryPR: Deprecate Unity Catalog function integration in AI Gateway (#19457) Unresolved Comments Addressed: 2 Changes Made
Commit Details
The changes are ready for review and all feedback has been addressed. |
serena-ruan
left a comment
There was a problem hiding this comment.
LGTM! Should we include this in 3.8.0?
|
Documentation preview for c608602 is available at: Changed Pages (1)
More info
|
- Make deprecation message more specific in Unity Catalog docs - Add alternative guidance link to deprecation warning 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: mlflow-app[bot] <mlflow-app[bot]@users.noreply.github.com>
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: mlflow-app[bot] <mlflow-app[bot]@users.noreply.github.com> Co-authored-by: Claude <noreply@anthropic.com>
🛠 DevTools 🛠
Install mlflow from this PR
For Databricks, use the following command:
Related Issues/PRs
#xxxWhat changes are proposed in this pull request?
Deprecate the Unity Catalog function integration feature in the MLflow AI Gateway:
FutureWarningwhenMLFLOW_ENABLE_UC_FUNCTIONSis enabledHow is this PR tested?
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
Unity Catalog function integration via the MLflow AI Gateway is now deprecated and will be removed in a future release.
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.
🤖 Generated with Claude Code