feat: Support for alternative vector databases in codebase indexing #6225
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.
Summary
This PR implements support for multiple vector database providers in the codebase indexing feature, addressing issue #6223.
Changes
Core Implementation
Configuration & Service Updates
Internationalization
Benefits
Testing
The implementation includes proper error handling for missing dependencies and dimension mismatches. Each adapter gracefully handles initialization failures and provides clear error messages.
Next Steps
Fixes #6223
Important
Adds support for multiple vector database providers in codebase indexing, including LanceDB, ChromaDB, and SQLite+Vector, with configuration and internationalization updates.
VectorDBAdapterbase class for vector database interface.LanceDB,ChromaDB, andSQLite+Vector.Qdrantimplementation to use adapter pattern.service-factory.tsfor dynamic vector database provider selection.config-manager.tsfor new configuration options:vectorDBProvider,chromadbUrl,chromadbApiKey.This description was created by
for 3a0a6d0. You can customize this summary. It will automatically update as commits are pushed.