-
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
pipe storage cp
shall start data upload before traversing full source hierarchy
#2574
Labels
Milestone
Comments
sidoruka
added
kind/enhancement
New feature or request
sys/cli
Issues related to the pipe cli
state/draft
Draft issues, that are lacking description or not ready for the implementation
goal/dorado ✨
labels
Mar 29, 2022
sidoruka
removed
the
state/draft
Draft issues, that are lacking description or not ready for the implementation
label
Mar 30, 2022
Backport to |
ekazachkova
added a commit
that referenced
this issue
Apr 6, 2022
…g full source hierarchy - s3 ls (WIP)
ekazachkova
added a commit
that referenced
this issue
Apr 11, 2022
…g full source hierarchy - s3 ls (WIP)
ekazachkova
added a commit
that referenced
this issue
Apr 11, 2022
…g full source hierarchy - async batch collection for cp/mv operation
ekazachkova
added a commit
that referenced
this issue
Apr 11, 2022
…g full source hierarchy - cleanups
ekazachkova
added a commit
that referenced
this issue
Apr 12, 2022
…g full source hierarchy - refactor cp/mv paging
ekazachkova
added a commit
that referenced
this issue
Apr 12, 2022
…g full source hierarchy - refactor cp/mv paging
ekazachkova
added a commit
that referenced
this issue
Jul 4, 2024
…g full source hierarchy (S3 provider) - cleanups
ekazachkova
added a commit
that referenced
this issue
Jul 4, 2024
…g full source hierarchy (S3 provider) - async batch
ekazachkova
added a commit
that referenced
this issue
Jul 4, 2024
…g full source hierarchy (S3 provider) - disable async batch by default
ekazachkova
added a commit
that referenced
this issue
Jul 4, 2024
…g full source hierarchy (S3 provider) - cleanup
ekazachkova
added a commit
that referenced
this issue
Jul 5, 2024
…g full source hierarchy (S3 provider) - cleanup
ekazachkova
added a commit
that referenced
this issue
Jul 5, 2024
…g full source hierarchy (S3 provider) - cleanup
ekazachkova
added a commit
that referenced
this issue
Jul 5, 2024
…g full source hierarchy (S3 provider) - cleanup
ekazachkova
added a commit
that referenced
this issue
Jul 8, 2024
…g full source hierarchy (S3 provider) - support local paths
ekazachkova
added a commit
that referenced
this issue
Jul 9, 2024
…g full source hierarchy (S3 provider) - cleanup
ekazachkova
added a commit
that referenced
this issue
Jul 9, 2024
…g full source hierarchy (S3 provider) - cleanup
SilinPavel
pushed a commit
that referenced
this issue
Jul 9, 2024
…g full source hierarchy (S3 and Local provider) (#2597)
ekazachkova
added a commit
that referenced
this issue
Jul 15, 2024
ekazachkova
added a commit
that referenced
this issue
Jul 31, 2024
SilinPavel
pushed a commit
that referenced
this issue
Jul 31, 2024
SilinPavel
pushed a commit
that referenced
this issue
Jul 31, 2024
SilinPavel
pushed a commit
that referenced
this issue
Jul 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Background
At the moment,
pipe storage cp/mv
CLI command for--recursive
operations runs (at least) in two phases:source
directory recursively and collect all the files/foldersFor huge filesystem hierarchies the
scan
process may take a lot of time (hours) and consume a lot of memory.Approach
It would be great to change the scanning procedure in a more asynchronous fashion, e.g.:
destination
The text was updated successfully, but these errors were encountered: