Story #3801
closedAs a user, I can skip to various pages for paginated results
0%
Description
We currently use cursor based pagination where pages must be fetched sequentially as opposed to the default DRF pagination method of using page numbers. Cursors work great for large data sets as you don’t have to figure out things like the number of pages.
The first problem is that in Pulp we parallelize web requests for things like fetching metadata. See our Ansible plugin as an example[1]. If we want to support things like syncing content from one Pulp server to another, we probably have to use offset/page-based pagination for certain endpoints.
Another consideration is Katello. In Katello’s UI they show the number of pages and allow users to jump to arbitrary pages or the last page. If we want Katello to stop indexing Pulp data and instead query Pulp directly, we’ll need to allow them to use page numbers somehow.
To change from cursor-based pagination to page number pagination, we simply need to extend PageNumberPagination in our base pagination models.
Related issues
Updated by daviddavis over 6 years ago
- Status changed from NEW to POST
- Assignee set to daviddavis
Added by daviddavis over 6 years ago
Added by daviddavis over 6 years ago
Revision 53f41330 | View on GitHub
Changing from cursor to page number pagination
Updated by daviddavis over 6 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp|53f413306467e6836082aaf5c965b63c6cd09d54.
Updated by rochacbruno about 6 years ago
- Related to Test #4221: As a user, I can skip to various pages for paginated results added
Updated by daviddavis over 5 years ago
- Tags Katello-P3 added
- Tags deleted (
Functional Test, Katello-P4)
Updated by bmbouter about 5 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Updated by ggainey over 4 years ago
- Tags Katello added
- Tags deleted (
Katello-P3)
Changing from cursor to page number pagination
fixes #3801 https://pulp.plan.io/issues/3801