Cursor
Describes efficient batch retrieval of large amounts of documents, cursor can get documents. The state of the result set is preserved.
- By default the cursor is not enabled. To enable it, select cursor to the GQL query to get the cursor in combination with a query in
where
using an empty string""
as value, such ascursor: ""
. - The response has a cursor value, and then gets the next batches using that cursor value in the GQL query.
- The results for the first query is preserved in the current state (stateful), 10 minutes per request, and after that time, the cursor expires and is no longer valid.
- Continue till there are no more results. The number of results per batch depends on the number set in limit. For the first query with cursor, the skip is ignored. The client can implement this by ignoring the first batches of results.
- You should sort by DOC for fastest retrieval.
- At least 1 content item field must be projected or else you will get an error. Only
total
is not sufficient because it is not a field of an item initems
.
Example request, where you get the batches per one document:
{
StandardPage(
cursor: "FGluY2x1ZGVfY29udGV4dF91dWlkDXF1ZXJ5QW5kRmV0Y2gBFnh3Qmszbmh0UkxPeWVGVHBLcUtQVWcAAAAAAAAATRZJVkJ4eFZBdVM5dTI4R1UzVUFSOEpn"
limit: 1
orderBy: {_ranking: DOC}
) {
items {
Name
Url
RouteSegment
Changed
}
cursor
}
}
Updated 4 months ago
Next