swift client psudeo-folder upload syntax for segmented objects uses wrong path
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-swiftclient |
Fix Released
|
Undecided
|
James Nzomo |
Bug Description
when you create a segmented object with a pseudo-folder syntax the _segment "container" is placed into the same container as the manifest?
swift upload test/crazy swift.tar.gz -S 1M --use-slo
results in *only* a container "test" and all the segments of the object are uploaded into the test container with a common prefix of crazy_segments/.
I'm don't believe this is intentional. It's definitely not documented to have this behavior.
I could imagine a usecase with container-
Changed in python-swiftclient: | |
assignee: | nobody → James Nzomo (moje) |
Changed in python-swiftclient: | |
status: | New → In Progress |
So currently, segmented object uploads done when <container> arg = `container/ pseudo- folder` results in "_segments" string being appended to the full pseudo path instead of the container_name only for the default segments container. (`container- name`_segments)
IMHO the right fix would be to split the container name and pseudo-folder, from <container> and prepend the latter to the SwiftObject's object_ name... essentially redoing https:/ /review. openstack. org/#/c/ 263259 the right way.