Skip to content
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

file-segments are downloaded when downloading a container at the top level #7879

cyberduck opened this issue Apr 8, 2014 · 1 comment


Copy link

@cyberduck cyberduck commented Apr 8, 2014

7a9fe78 created the issue

It appears that cyberduck is downloading the .file-segments folder along with the unsegmented large files when downloading container in its entirety.

This is extremely undesirable behaviour as your ending up with double the amount of data being transferred if you container consists purely of large objects.

We have been able to circumvent the issue by including .file-segments include the list of download filtered files Preferences → Transfers → Filter.

Fundamentally you want to decouple file segments from the users container, my short term suggestion would be to include .file_segments to the default list of filtered filter.

Longer term I would suggest getting taking the approach of creating .file-segments into its own container, a similar approach to the python swift client.

You could then put some logic in place to calculate the size of the container based on the external file segments container.

Quick note: This was testing on the 4.4.3 Stable build for windows however it may impact other platforms as I presume the logic is shared.

Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 8, 2014

@dkocher commented

Added to default regular expression download filter in aafe821. Rewriting our segment feature to store segments in a different container is not currently an option.


@cyberduck cyberduck closed this Apr 8, 2014
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants