Skip to content

Deprecate Unity Catalog function integration in AI Gateway#19457

Merged
harupy merged 3 commits intomlflow:masterfrom
harupy:deprecate-uc-functions
Dec 17, 2025
Merged

Deprecate Unity Catalog function integration in AI Gateway#19457
harupy merged 3 commits intomlflow:masterfrom
harupy:deprecate-uc-functions

Conversation

@harupy
Copy link
Member

@harupy harupy commented Dec 17, 2025

🛠 DevTools 🛠

Open in GitHub Codespaces

Install mlflow from this PR

# mlflow
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/19457/merge
# mlflow-skinny
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/19457/merge#subdirectory=libs/skinny

For Databricks, use the following command:

%sh curl -LsSf https://raw.githubusercontent.com/mlflow/mlflow/HEAD/dev/install-skinny.sh | sh -s pull/19457/merge

Related Issues/PRs

#xxx

What changes are proposed in this pull request?

Deprecate the Unity Catalog function integration feature in the MLflow AI Gateway:

  • Add deprecation warning in the documentation
  • Emit FutureWarning when MLFLOW_ENABLE_UC_FUNCTIONS is enabled
  • Update the environment variable docstring to indicate deprecation

How is this PR tested?

  • Existing unit/integration tests
  • New unit/integration tests
  • Manual tests

Does this PR require documentation update?

  • No. You can skip the rest of this section.
  • Yes. I've updated:
    • Examples
    • API references
    • Instructions

Release Notes

Is this a user-facing change?

  • No. You can skip the rest of this section.
  • Yes. Give a description of this change to be included in the release notes for MLflow users.

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, autologging
  • area/models: MLmodel format, model serialization/deserialization, flavors
  • area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
  • area/scoring: MLflow Model server, model deployment tools, Spark UDFs
  • area/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflows
  • area/gateway: MLflow AI Gateway client APIs, server, and third-party integrations
  • area/prompts: MLflow prompt engineering features, prompt templates, and prompt management
  • area/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionality
  • area/projects: MLproject format, project running backends
  • area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
  • area/build: Build and test infrastructure for MLflow
  • area/docs: MLflow documentation pages

How 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" section
  • rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
  • rn/feature - A new user-facing feature worth mentioning in the release notes
  • rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
  • rn/documentation - A user-facing documentation change worth mentioning in the release notes

Should 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?
  • 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)

🤖 Generated with Claude Code

Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
Copilot AI review requested due to automatic review settings December 17, 2025 09:34
@github-actions github-actions bot added area/docs Documentation issues rn/feature Mention under Features in Changelogs. labels Dec 17, 2025
@harupy harupy added the team-review Trigger a team review request label Dec 17, 2025
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 FutureWarning when MLFLOW_ENABLE_UC_FUNCTIONS is 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.

@harupy
Copy link
Member Author

harupy commented Dec 17, 2025

/resolve


🚀 Resolve workflow started


✅ Workflow completed successfully.

Claude Output

Perfect! I've successfully addressed all unresolved PR review comments for PR #19457. Here's what was done:

Summary

PR: Deprecate Unity Catalog function integration in AI Gateway (#19457)

Unresolved Comments Addressed: 2

Changes Made

  1. Updated deprecation message in documentation (docs/docs/genai/governance/unity-catalog.mdx:5)

    • Made the deprecation warning more specific and clear
    • Changed from generic "This feature is deprecated" to "Unity Catalog function integration via the MLflow AI Gateway is deprecated and will be removed in a future release."
  2. Added alternative guidance to deprecation warning (mlflow/gateway/providers/openai.py:561-567)

Commit Details

  • Commit: 86304ee
  • All pre-commit hooks passed successfully
  • Changes committed locally with DCO sign-off
  • Not pushed to remote (as per instructions)

The changes are ready for review and all feedback has been addressed.

Copy link
Collaborator

@serena-ruan serena-ruan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Should we include this in 3.8.0?

@github-actions
Copy link
Contributor

github-actions bot commented Dec 17, 2025

Documentation preview for c608602 is available at:

Changed Pages (1)

More info
  • Ignore this comment if this PR does not change the documentation.
  • The preview is updated when a new commit is pushed to this PR.
  • This comment was created by this workflow run.
  • The documentation was built by this workflow run.

- 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>
@harupy harupy added this pull request to the merge queue Dec 17, 2025
Merged via the queue into mlflow:master with commit 1677244 Dec 17, 2025
46 checks passed
@harupy harupy deleted the deprecate-uc-functions branch December 17, 2025 10:42
WeichenXu123 pushed a commit to WeichenXu123/mlflow that referenced this pull request Dec 19, 2025
)

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>
WeichenXu123 pushed a commit that referenced this pull request Dec 19, 2025
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/docs Documentation issues rn/feature Mention under Features in Changelogs. team-review Trigger a team review request v3.8.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants