jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Gaul (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCLOUDS-1285) Store Swift large object segments in a separate container
Date Tue, 03 Apr 2018 15:57:00 GMT

     [ https://issues.apache.org/jira/browse/JCLOUDS-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Gaul updated JCLOUDS-1285:
---------------------------------
    Summary: Store Swift large object segments in a separate container  (was: Store large
object segments in a separate container)

> Store Swift 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
>            Priority: Major
>              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
(v7.6.3#76005)

Mime
View raw message