Skip to main content
Besides the upsert operation which has 6MB maximum payload size limit, LambdaDB also supports bulk upsert operation to insert or update multiple documents up to 200MB at once.
Bulk upsert is not supported for collections that contain managed embedding vector fields. Use the regular upsert or update flow so LambdaDB can generate embeddings from the configured source text fields.
The easiest way to bulk upsert is to use the SDK’s one-step method. The client uploads your documents to the presigned URL and completes the bulk upsert for you (up to 200MB).
After a successful request you’ll receive a message such as "Upsert request is accepted". Documents are processed asynchronously and become searchable after indexing completes.

Two-step: Get presigned URL, then upload and complete

If you need to control the upload yourself (e.g. from a different process or storage), use this flow: (1) get bulk upsert info (presigned URL and objectKey), (2) upload the payload to the presigned URL, then (3) call the bulk-upsert API with the objectKey.

Step 1: Get bulk upsert information

Response:

Step 2: Upload to presigned URL and call bulk-upsert

Upload the document list as JSON to the url (PUT), then call the bulk-upsert API with the objectKey from step 1.

Response

After successful bulk upsert initiation you’ll receive:
Bulk upsert operations are processed asynchronously in the background. Consequently, newly uploaded documents may not be immediately available for search or fetch requests, even if consistentRead (Python: consistent_read) is set to true. The documents will become available only after the indexing process is fully complete.