-
Notifications
You must be signed in to change notification settings - Fork 6
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
Paging in unordered collections #58
Comments
Adding the query we were working with:
Using this for query vars:
|
RDPC-gateway changes to queries for
See example illustrating new changes with
Now (sorts is a new query param wasn't there before):
|
Notes about services that are connected to this feature:
|
Confirmed on release Jan 22; new query format is available at https://api.rdpc.cancercollaboratory.org/graphql |
From Investigation in icgc-argo/donor-submission-aggregator#122, repeated queries to the rdpc-api is showing that the order of the response from rdpc is not guaranteed.
So when we pull 3 pages, there could be duplicated or missing analyses
It should be default sorted by the object-id (analysisid, run, id etc)
Workflow search has this:
https://github.com/icgc-argo/workflow-search/blob/develop/src/main/java/org/icgc_argo/workflow/search/repository/RunRepository.java#L107-L109
Song-search needs something like this:
https://github.com/icgc-argo/song-search/blob/develop/src/main/java/bio/overture/songsearch/repository/AnalysisRepository.java#L136-L147
Include additional paging information from the graphql api:
have the total number of hits, total returned in this page, and an indicator if there are more pages
currently, we get no page data back in the responses, so if we made our size param greater than your max size we would have to guess if there are more pages or if you just limited the search size
Please note if this is a breaking-change for workflow-ui. We need to update there with this ticket if so.
The text was updated successfully, but these errors were encountered: