Feature #17074
Updated by Peter Amstutz 8 months ago
Calculating "items_available" in list requests is expensive. For example, on a user cluster, they have a project with over 2 million collections and it takes around 10 seconds to return 50 items. On another user cluster, they have 600,000 projects and the "shared with me" groups list takes over 5 seconds to return 50 items. If we use "count=none" then it will skip having to the count all rows and results can be returned much faster. Using "offset" for paging is also expensive, because it throws away results. Without knowing the total count, offset paging cannot provide a "navigate to last page" option, as it does not know how many pages there are. Offset paging also produces unexpected results if list order changes during navigation. We want to make the following changes: # all list requests use count=none unless there's some special reason it needs it (for example, displaying the total number of search results) # paging is adjusted to use keyset paging. Results are ordered by [sort column, uuid] and the search query uses something like [sort column >= last seen, uuid > last seen]. # User can navigate to first page, last page, next page, previous page. User cannot navigate to an arbitrary page. # The last seen sort column and uuid should be included in the query part of the URL in the URL bar so that someone can still copy and paste a logical link to the page.