You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We do delete segments of large file uploads when connected to OpenStack Swift. My understanding is that when connecting with S3 interoperability this would be the responsibility of the server as S3 does not have such a concept.
Here is another aspect I observed: When I issue a normal delete, the chunks in +segments folder is deleted properly. It's only with overwrites that I hit the issue.
Here is another aspect I observed: When I issue a normal delete, the chunks in +segments folder is deleted properly. It's only with overwrites that I hit the issue.
Overwriting files from a transfer will not explicitly delete files and thus we do not handle this use case.
I have noticed that when we overwrite a file with s3 protocol, the data chunks are still present for both the upload id in +segments container.
Storage: Openstack Swift - S3 Compatible.
Steps to reproduce the bug.
Expected behavior: Data chunks in older upload ID folder should have been deleted.
Cyberduck Version: 7.9.2
Platform: Mac, Windows
Screenshots:
Two folders with different upload ID after successful overwrite: https://imgur.com/S4hY9zY
Screenshot from Cyberduck showing successful overwrite: https://imgur.com/b1zTVlZ
Attachments
S4hY9zY - Imgur.png
(22.1 KiB)b1zTVlZ - Imgur.png
(27.6 KiB)The text was updated successfully, but these errors were encountered: