Container name length will increase with every "swift upload" request for manifest file.
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>
Suggested solution:
A condition statement has to be implemented in _update_or_create() method called from PUT function of /swift/
affects: | swift → python-swiftclient |
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.