Skip to content

docs(api): the batch cap is embedder-only, not the deployment's to configure #17185

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
baozhoutao merged 1 commit into from
Sep 9, 2026
+7 −3
Merged

docs(api): the batch cap is embedder-only, not the deployment's to configure #17185

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
10 changes: 7 additions & 3 deletions content/docs/api/data-api.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -323,9 +323,13 @@ prior delete, and the response reports `succeeded: 0` with each row's
### Batch size

Every bulk route above — `batch`, `createMany`, `updateMany`, `deleteMany` —
caps how many records one request may carry. The limit is the deployment's
`batch.maxBatchSize` (default **200**, configurable 1–1000); over it the request
is rejected with `400 BATCH_TOO_LARGE` before anything is written:
caps how many records one request may carry. The limit is
`batch.maxBatchSize`, and it is **embedder-only** (#15543): it is written only
by a host that constructs the `RestServerConfig` itself, never by `os serve` or
the dev plugin. A CLI-started deployment therefore always gets the default of
**200**, and no flag, config file or CLI option moves it; only the embedding
host can set it, anywhere in 1–1000. Over the cap the request is rejected with
`400 BATCH_TOO_LARGE` before anything is written:

```json
{
Expand Down
Loading