Improve AnalyticDB Vector Store implementation without affecting user #6086
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.
Hi there:
As I implement the AnalyticDB VectorStore use two table to store the document before. It seems just use one table is a better way. So this commit is try to improve AnalyticDB VectorStore implementation without affecting user behavior:
1. Streamline the
post_init
behavior by creating a single table with vector indexing.2. Update the
add_texts
API for document insertion.3. Optimize
similarity_search_with_score_by_vector
to retrieve results directly from the table.4. Implement
_similarity_search_with_relevance_scores
.5. Add
embedding_dimension
parameter to support different dimension embedding functions.Users can continue using the API as before.
Test cases added before is enough to meet this commit.