Skip to content

mason: require mlflow>=3.10.1 for tracing (was 3.9.0) - #549

Merged
elainewang-db merged 2 commits into
databricks:mainfrom
elainemwang:mason-bump-tracing-mlflow
Sep 4, 2026
Merged

mason: require mlflow>=3.10.1 for tracing (was 3.9.0)#549
elainewang-db merged 2 commits into
databricks:mainfrom
elainemwang:mason-bump-tracing-mlflow

Conversation

@elainewang-db

Copy link
Copy Markdown
Contributor

mason tracing setup uses UC trace destinations (set_experiment_trace_location, UCSchemaLocation), which is why users hit 'This MLflow version is too old'. The tracing extra floored mlflow at >=3.9.0 while both runtime extras already require >=3.10.1 — bump tracing (and its install hints) to match.

mason tracing setup uses UC trace destinations (set_experiment_trace_location,
UCSchemaLocation), which is why users hit 'This MLflow version is too old'. The
tracing extra floored mlflow at >=3.9.0 while both runtime extras already
require >=3.10.1 — bump tracing (and its install hints) to match.

Co-authored-by: Isaac <no-reply@databricks.com>
The missing/too-old-mlflow errors told users to pip install a bare mlflow, but
what actually fixes both cases is installing the extra — it carries the version
floor mason tracing needs and upgrades a stale mlflow already in the venv.

Co-authored-by: Isaac <no-reply@databricks.com>
@elainewang-db
elainewang-db merged commit 1c9123c into databricks:main Sep 4, 2026
50 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants