[
https://issues.apache.org/jira/browse/JCLOUDS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995289#comment-15995289
]
Andrew Gaul commented on JCLOUDS-1285:
--------------------------------------
This would make Swift work more like S3 by not showing the MPU parts in
container listings and avoiding users deleting parts. We should plug a few
other leaky abstractions like deleting the segments container when deleting the
parent container and perhaps eliding the segments containers from container
listings.
> Store large object segments in a separate container
> ---------------------------------------------------
>
> Key: JCLOUDS-1285
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1285
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-blobstore
> Affects Versions: 2.0.1
> Reporter: Timur Alperovich
> Labels: openstack-swift
>
> Swift recommends storing the large object segments in a separate container
> [1]. I propose changing jclouds to do the same. The Swift convention -- in
> their python library -- is to create a "<container>_segments" container for
> the segments.
> We need to consider ways to reduce the number of HEAD requests jclouds would
> make for container existence. One possible way could be to assume the
> container exists for the segments and create it if the PUT requests return
> 404. I will need to look through the existing MPU abstraction to figure out
> the other caveats to work out in this improvement.
> 1. https://docs.openstack.org/developer/swift/overview_large_objects.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
