Expiring Large Object interaction is not explicit
Bug #1514606 reported by
clayg
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Object Storage (swift) |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
### DLO
Obviously expirer has no idea about the segments of this DLO object.
### SLO
The expirer doesn't have ?multipart-
If a user is expecting adding an expirer header to a manifest to delete the segments they will be disappointed.
We should have functional tests to describe the interaction [1] and update the docs to explain and reference the expected behavior.
1. ProTip: they *don't interact. However client tooling to could better to add expirer headers when creating segments if it's going to expire the manifest lp bug #1514604
| Changed in swift: | |
| assignee: | nobody → Sirisha Guduru (guduru-sirisha) |
| status: | New → In Progress |
| assignee: | Sirisha Guduru (guduru-sirisha) → nobody |
| status: | In Progress → New |
| Changed in swift: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
To post a comment you must log in.
