[Bug] autoPagination limited at 6000 entities
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- graphql, typescript
- Domain
- api, backend-api-design
Research direction
Reproduce the limit using .graphclientrc.yml, test.graphql, and the generated TestQueryDocument with execute. Start by reading the autoPagination README and its implementation entry point, then determine how pagination behaves when skip exceeds 5000. Done means the documented query returns more than 6000 entities without the skip validation error, with coverage for this case.
Written by the indexing model from the issue text.
Description
I have having some problems with the autoPagination feature. It seems I am unable to get more than 6000 items due to:
message: The skip argument must be between 0 and 5000, but is 6000
I followed the docs from here:
- https://thegraph.com/docs/en/querying/querying-from-an-application/#graphql-clients
- https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md
My .graphclientrc.yml is:
sources:
- name: test
handler:
graphql:
endpoint: https://api.thegraph.com/subgraphs/name/papercliplabs/compound-v3-mainnet
transforms:
- autoPagination:
validateSchema: true
documents:
- ./test.graphql
My test.graphql is:
query TestQuery {
transactions(first: 10000) {
id
}
}
And I am executing the query like so:
import { execute, TestQueryDocument } from "./.graphclient";
const result = await execute(TestQueryDocument, {});
console.log(result);
Looks like others are having the same issue
This is not really "Unlimited Pagination" as the docs say, so seems there is a bug here.
If this skip of 5000 is a limitation in the graph node, the client can still filter by ID and serve more than 6000
- Dominant language
- TypeScript
- Stars
- 186
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from graphprotocol/graph-client
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
graphprotocol/graph-client#1029 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
graphprotocol/graph-client#1031 · 4 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
graphprotocol/graph-client#1001 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 50/100
graphprotocol/graph-client#991 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 28/100
graphprotocol/graph-client#957 ·
All issues in graphprotocol/graph-client
Similar issues
-
VerificationGate: ATTRIBUTION quote guard never matches a normal quotation (\b around the quote) Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
danielmiessler/LifeOS#2234 ·
-
T: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 70/100