Container name length will increase with every "swift upload" request for manifest file.

Bug #1699981 reported by Saurabh jangir
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-swiftclient
New
Undecided
Unassigned

Bug Description

When a Static Large Object (SLO) is uploaded to a container (ContainerName) in segments with a manifest file, a new container is created with name <containerName>_segments. If we repeat the same operation (i.e upload an object) to the newly created container (<containerName>_segments), again a new container is created named <ContainerName>_segments_segments containing the multipart segments. This process continues for each "SLO-upload" request. This design is inconvenient to manage since container name length will increase with every request.

Suggested solution:

A condition statement has to be implemented in _update_or_create() method called from PUT function of /swift/container/server.py, which would check whether a segmented container is already present. If yes, the new segmented files must be uploaded to the previously created containerName_segments .

Tim Burke (1-tim-z)
affects: swift → python-swiftclient
Revision history for this message
Tim Burke (1-tim-z) wrote :

You're describing a client behavior -- the segments for a large object can be in any container within the same account; it's up to the client what naming conventions to use. That said, swiftclient is behaving as expected: whatever container you're uploading to (whether that's "ContainerName" or "ContainerName_segments"), it will create the large object in <container> and default to putting the segments in <container>_segments (so, "ContainerName_segments" or "ContainerName_segments_segments", respectively). You can override this with the --segment-container option.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.