Reverse Object Listing
Goal: Enable the ability to paginate backwards through a container listing. It's possible using the current API to paginate going forward using limit and marker. It's not possible to go the other way using end_marker and limit because the limit applies to the beginning of the listing. Another use-case for a reverse listing is getting a listing of the latest objects in a container with date-sorted log files. I propose we introduce a 'reverse' parameter to the container GET call that will query the container sorted in descending order.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Kevin McDonald
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Solution: Add a reverse parameter to the container call: v1/{account}
reverse (Optional) - Flag that reverses the order of the object listing, either true or false.
Gerrit topic: https:/
Addressed by: https:/
Initial Implementation of reverse-
Addressed by: https:/
Add container reverse listings and basic ordering
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
Add more functional tests for reverse listings
Addressed by: https:/
Reverse-
Gerrit topic: https:/
Addressed by: https:/
Merge branch 'master' into feature/crypto
Gerrit topic: https:/
Addressed by: https:/
Merge branch 'master' into feature/hummingbird
