-
Notifications
You must be signed in to change notification settings - Fork 59
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
Issue #2574: pipe storage cp shall start data upload before traversing full source hierarchy (S3 provider) #2597
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…g full source hierarchy (WIP)
…g full source hierarchy - s3 ls (WIP)
…g full source hierarchy - async batch collection for cp/mv operation
…g full source hierarchy - cleanups
…ipe-storage-cp # Conflicts: # pipe-cli/src/utilities/datastorage_operations.py
tcibinan
reviewed
Apr 12, 2022
…g full source hierarchy - refactor cp/mv paging
…g full source hierarchy - refactor cp/mv paging
tcibinan
approved these changes
Apr 12, 2022
…_2574-batch-pipe-storage-cp # Conflicts: # pipe-cli/src/utilities/datastorage_operations.py # pipe-cli/src/utilities/storage/s3.py
…_2574-batch-pipe-storage-cp
…g full source hierarchy (S3 provider) - cleanups
…g full source hierarchy (S3 provider) - async batch
…g full source hierarchy (S3 provider) - disable async batch by default
…g full source hierarchy (S3 provider) - cleanup
…g full source hierarchy (S3 provider) - cleanup
…g full source hierarchy (S3 provider) - cleanup
…g full source hierarchy (S3 provider) - cleanup
…g full source hierarchy (S3 provider) - support local paths
…g full source hierarchy (S3 provider) - cleanup
…g full source hierarchy (S3 provider) - cleanup
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current PR provides implementation for issue #2574
pipe storage cp/mv
operations - this feature enables for:--verify-destination
shall not be enabled (since this option required full source listing)--file-list
shall not be enabledpipe storage ls
operation - full listing enables for:--recursive
options shall be specified--show_versions
shall not be specified--page
size limit shall not be specifiedpipe storage rm
operations - added page size support for S3 providerbatch size can be tuned via
CP_CLI_STORAGE_BATCH_SIZE
environment variable (default: 1000)CP_CLI_STORAGE_ASYNC_BATCH_ENABLE=[True|False]
- enables asynchronous batch transfer - listing operation performs in separate thread (default: False)