GH-3540: Allow user-provided embeddings in VectorStore #3541
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🚀 Motivation
Current VectorStore implementations (e.g., ChromaVectorStore) automatically generate embeddings from Document.content using the configured EmbeddingModel. However, more advanced use cases require greater flexibility:
🔧 Enhancement
This PR introduces support for user-supplied embeddings, allowing applications to decouple document storage from semantic representation. This separation enables more accurate and intentional embedding strategies for search and retrieval.
✅ Backward Compatibility
Fully maintained. The default pipeline continues to auto-generate embeddings when none are explicitly provided.
🧪 Testing & Limitations
This feature has been tested with SimpleVectorStore. Other implementations (e.g., Pinecone, Milvus) were not tested due to environment constraints and may require further validation or adapter adjustments.
✅ Issue Closed
Closes #3540