-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unification: Package search result pagination #1462
Comments
This is related to a comment I made on your PR: I think we should consider doing the searching and pagination in |
FWIW it only requires two, but yes it's a giant amount of data. eg. If you look at the output from
And then requests all of them in one query with limit set to the total count:
It would be much more efficient to implement the searching on the server side like Tom suggests. |
@lucasgarfield Any additional information about this issue? |
We would like to eliminate pagination from the package search feature. This would allow us to perform our own (better) sorting logic similar to what is done in Image Builder Front End.
Currently, searching for packages is done by calling the Weldr API, which supports* pagination. *In a sense it requires pagination. On my machine, requests for > ~1000 packages fail.
Therefore, changes to the Weldr API are probably necessary to implement this effectively as fetching the full package list would require a very large number of API calls (consider that Fedora has ~35k packages).
The text was updated successfully, but these errors were encountered: