Skip to content

DOC-647 | Clarify the presence of nextBatchId #417

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

Merged
merged 1 commit into from
Jan 8, 2024
Merged

DOC-647 | Clarify the presence of nextBatchId #417

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions site/content/3.11/develop/http-api/queries/aql-queries.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -178,9 +178,9 @@ Content-type: application/json
}
```

If the `allowRetry` query option is set to `true`, then the response object
contains a `nextBatchId` attribute, except for the last batch (if `hasMore` is
`false`). If retrieving a result batch fails because of a connection issue, you
The response object contains a `nextBatchId` attribute, except for the last batch
(when `hasMore` is `false`). If the `allowRetry` query option is set to `true`
and if retrieving a result batch fails because of a connection issue, you
can ask for that batch again using the `POST /_api/cursor/<cursor-id>/<batch-id>`
endpoint. The first batch has an ID of `1` and the value is incremented by 1
with every batch. Every result response except the last one also includes a
Expand Down
6 changes: 3 additions & 3 deletions site/content/3.12/develop/http-api/queries/aql-queries.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -178,9 +178,9 @@ Content-type: application/json
}
```

If the `allowRetry` query option is set to `true`, then the response object
contains a `nextBatchId` attribute, except for the last batch (if `hasMore` is
`false`). If retrieving a result batch fails because of a connection issue, you
The response object contains a `nextBatchId` attribute, except for the last batch
(when `hasMore` is `false`). If the `allowRetry` query option is set to `true`
and if retrieving a result batch fails because of a connection issue, you
can ask for that batch again using the `POST /_api/cursor/<cursor-id>/<batch-id>`
endpoint. The first batch has an ID of `1` and the value is incremented by 1
with every batch. Every result response except the last one also includes a
Expand Down