[Cyberduck-trac] [Cyberduck] #7879: file-segments are downloaded when downloading a container at the top level

[Cyberduck]

#7879: file-segments are downloaded when downloading a container at the top level
-----------------------+-------------------------
 Reporter:  jpereira   |         Owner:  dkocher
     Type:  defect     |        Status:  assigned
 Priority:  high       |     Milestone:  4.4.4
Component:  openstack  |       Version:  4.4.3
 Severity:  major      |    Resolution:
 Keywords:             |  Architecture:  Intel
 Platform:  Windows 7  |
-----------------------+-------------------------
Changes (by dkocher):

 * status:  new => assigned


Old description:

> 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.

New description:

 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.

--

-- 
Ticket URL: <https://trac.cyberduck.io/ticket/7879#comment:1>
Cyberduck <http://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows