Managed embeddings let LambdaDB generate vector values from a source text field and store them in a managedDocumentation Index
Fetch the complete documentation index at: https://docs.lambdadb.ai/llms.txt
Use this file to discover all available pages before exploring further.
vector field.
Use managed embeddings when you want LambdaDB to own:
- embedding model selection
- vector generation during document writes
- query embedding generation for vector search
Supported providers
LambdaDB currently supports the following embedding provider:| Provider | Status |
|---|---|
openai | Supported |
Supported models
The following OpenAI embedding models are currently supported for managed embedding vector fields.| Model | Default dimensions | Dimensions parameter | Similarity |
|---|---|---|---|
text-embedding-3-small | 1536 | Optional, from 1 to 1536 | cosine |
text-embedding-3-large | 3072 | Optional, from 1 to 3072 | cosine |
text-embedding-ada-002 | 1536 | Fixed at 1536 | cosine |
Collection schema
Define a managed embedding vector field withmanagedEmbedding: true and an embedding block.
Schema rules
embedding.provideris requiredembedding.modelis requiredembedding.sourceFieldis requiredembedding.sourceFieldmust reference atextfield in the same collection- managed embedding vector fields must not use top-level
dimensions - managed embedding vector fields must not use top-level
similarity - LambdaDB resolves and stores the effective
embedding.dimensionsandembedding.similarity
Write behavior
For managed embedding vector fields, send the source text field and let LambdaDB generate the vector value. Do not send direct vector values for managed embedding fields in: Example upsert payload:Query behavior
For managed embedding vector fields, useknn.queryText instead of knn.queryVector.
Bulk upsert
bulk upsert is not supported for collections that contain managed embedding vector fields.
Use the regular document write flow instead: