-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GC CLI SFTP Support: implement delete_artifacts in sftp_artifact_repository #4670
Conversation
…sitory Signed-off-by: Alexander Faul <kontakt-github-signature@afaul.de>
Do you mind adding some unit tests for the proposed change? Existing tests are located at tests/store/artifact/test_sftp_artifact_repo.py. Thank you! |
Signed-off-by: Alexander Faul <kontakt-github-signature@afaul.de>
I added two tests for the deletion of artifacts. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding the tests. LGTM overall. Some minor comments. Please also fix the lint issue by following recommendations from ./lint.sh.
…don't deletes to much and reformated the file with black as lint.sh suggested Signed-off-by: Alexander Faul <kontakt-github-signature@afaul.de>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's still formatting error: the lint test didn't pass. Please fix. Otherwise LGTM. Thanks for contributing to MLflow codebase!
…sitory (mlflow#4670) * GC CLI SFTP Support: implement delete_artifacts in sftp_artifact_repository Signed-off-by: Alexander Faul <kontakt-github-signature@afaul.de> * unit tests for deletion of artifacts via sftp added Signed-off-by: Alexander Faul <kontakt-github-signature@afaul.de> * made suggested changes, added another test to make sure the function don't deletes to much and reformated the file with black as lint.sh suggested Signed-off-by: Alexander Faul <kontakt-github-signature@afaul.de> * Fixed lint Co-authored-by: Alexander Faul <kontakt-github-signature@afaul.de> Co-authored-by: jinzhang21 <jin.zhang@databricks.com> Signed-off-by: Anjali Samad <samad.anjali.14@gmail.com>
Signed-off-by: Alexander Faul kontakt-github-signature@afaul.de
What changes are proposed in this pull request?
Implementation of delete_artifacts in sftp_artifact_repository.py
How is this patch tested?
(Details)
Release Notes
Is this a user-facing change?
(Details in 1-2 sentences. You can just refer to another PR with a description if this PR is part of a larger change.)
What 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/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