You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Derive artifact location from MLFLOW_TRACKING_URI env var too
When MLFLOW_TRACKING_URI was set as an environment variable (not the
tracking_uri argument) to a local SQLite database, the handler did not
co-locate run artifacts next to the db file, so they went to MLflow's
default mlruns directory relative to the working directory. An
argument-passed SQLite URI did get a sibling mlruns. Resolve an
effective tracking URI from the argument or the env var and key the
artifact-location logic off it, while still passing only tracking_uri to
the client so MLflow keeps resolving the env var. Add a regression test
for the env-var SQLite case.
Signed-off-by: Lawson Darrow <lawson.darrow@gmail.com>
0 commit comments