Pagination support should be added to Nailgun REST API

Registered by Nikolay Markov

This blueprint has been superseded. See the newer blueprint "Nailgun API pagination" for updated plans.

Currently we can receive any number of objects through API, it may be thousands. Let's discuss and implement common approach for pagination in API to decrease load and improve user experience.

Blueprint information

Status:
Complete
Approver:
Nikolay Markov
Priority:
Low
Drafter:
Nikolay Markov
Direction:
Approved
Assignee:
Nikolay Markov
Definition:
Superseded
Series goal:
Accepted for future
Implementation:
Good progress
Milestone target:
milestone icon next
Started by
Nikolay Markov
Completed by
Ihor Kalnytskyi

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/nailgun-rest-api-pagination,n,z

Addressed by: https://review.openstack.org/84698
    REST API Pagination prototype

Addressed by: https://review.openstack.org/84774
    Notication object - preparing for pagination

Gerrit topic: https://review.openstack.org/#q,topic:bp/nailgun-objects-flow,n,z

Addressed by: https://review.openstack.org/87218
    Nailgun pagination compatibility

Addressed by: https://review.openstack.org/87246
    Nailgun pagination compatibility

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.