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.

Sign up for GitHub

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

Jump to bottom

Collections: page size vs limit #2626

Open

josephjclark opened this issue Nov 1, 2024 · 0 comments

Assignees

Contributor

josephjclark commented Nov 1, 2024 •

edited

Loading

How do we handle page size and limit in the collections API? The two are different

limit is the total number of values to be returned
page size is the amount of of values returned in a single request

The distinction is that the socket will timeout if the page size is too large

I think where we're landing is:

users in the adaptor will specify a limit (the total number of records to return). A cursor will be returned to the user if there are more records to fetch
the server will ONLY support pagesize (not an absolute limit). Ie, get me 1000 values from X
the adaptor will handle pagination to return the correct number of values

josephjclark assigned stuartc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment