Deprecate duplicate artifact download APIs#6537
Deprecate duplicate artifact download APIs#6537WeichenXu123 merged 6 commits intomlflow:branch-2.0from
Conversation
Signed-off-by: Weichen Xu <[email protected]>
Signed-off-by: Weichen Xu <[email protected]>
|
shall we add an argument “tracking_uri” for |
Ah, that's definitely a problem. Good catch! Can we add |
Signed-off-by: Weichen Xu <[email protected]>
Signed-off-by: Weichen Xu <[email protected]>
2f0d27a to
d29822b
Compare
mlflow/artifacts/__init__.py
Outdated
| if tracking_uri is not None: | ||
| with _use_tracking_uri(tracking_uri): | ||
| store = _get_store() | ||
| else: | ||
| store = _get_store() |
There was a problem hiding this comment.
| if tracking_uri is not None: | |
| with _use_tracking_uri(tracking_uri): | |
| store = _get_store() | |
| else: | |
| store = _get_store() | |
| store = _get_store(tracking_uri) |
Can we pass tracking_uri to _get_store?
| """ | ||
| return self._tracking_client.list_artifacts(run_id, path) | ||
|
|
||
| @deprecated("mlflow.artifacts.download_artifacts", "2.0") |
There was a problem hiding this comment.
We can address this issue in a separate PR.
There was a problem hiding this comment.
I will file a follow-up PR to fix this.
There was a problem hiding this comment.
@WeichenXu123 You don't need to because I already did in #6552.
harupy
left a comment
There was a problem hiding this comment.
Left #6537 (comment), otherwise LGTM!
Signed-off-by: Weichen Xu <[email protected]>
Signed-off-by: Weichen Xu <[email protected]>

Signed-off-by: Weichen Xu [email protected]
Related Issues/PRs
#xxx
What changes are proposed in this pull request?
Deprecate duplicate artifact download APIs.
The following APIs are removed:
How is this patch tested?
Unit tests.
Does this PR change the documentation?
Detailslink on thePreview docscheck.Release Notes
Is this a user-facing change?
Deprecate duplicate artifact download API:
MlflowClient.download_artifactsWhat component(s), interfaces, languages, and integrations does this PR affect?
Components
area/artifacts: Artifact stores and artifact loggingarea/build: Build and test infrastructure for MLflowarea/docs: MLflow documentation pagesarea/examples: Example codearea/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registryarea/models: MLmodel format, model serialization/deserialization, flavorsarea/pipelines: Pipelines, Pipeline APIs, Pipeline configs, Pipeline Templatesarea/projects: MLproject format, project running backendsarea/scoring: MLflow Model server, model deployment tools, Spark UDFsarea/server-infra: MLflow Tracking server backendarea/tracking: Tracking Service, tracking client APIs, autologgingInterface
area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/docker: Docker use across MLflow's components, such as MLflow Projects and MLflow Modelsarea/sqlalchemy: Use of SQLAlchemy in the Tracking Service or Model Registryarea/windows: Windows supportLanguage
language/r: R APIs and clientslanguage/java: Java APIs and clientslanguage/new: Proposals for new client languagesIntegrations
integrations/azure: Azure and Azure ML integrationsintegrations/sagemaker: SageMaker integrationsintegrations/databricks: Databricks integrationsHow should the PR be classified in the release notes? Choose one:
rn/breaking-change- The PR will be mentioned in the "Breaking Changes" sectionrn/none- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" 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 notes