Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jim/vectordb update #106

Merged
merged 47 commits into from
Nov 1, 2024
Merged

Jim/vectordb update #106

merged 47 commits into from
Nov 1, 2024

Conversation

jimmoffet
Copy link
Collaborator

@jimmoffet jimmoffet commented Oct 29, 2024

Changelog Entry

Description

  • Switch vector store from chrome in memory to a remote redis server using Redis VL to handle vector operations. Other minor changes to UI.

Added

  • vector_client.py provides a client class and a collection class that wraps both chroma and redis and provides a single interface for both and VECTOR_STORE flag to plug them in and out. Very minor tests for this that need better mocks.
  • also added asynchronous embedding calls to Azure embedding endpoint, vector-indexing uploaded docs is much faster now

Changed

  • Lots of minor changes to look and feel.

Deprecated

  • Chroma hasn't really been tested after implementing the new interface, it should be removed and postgres with PGVector added as an alternative to redis (better for larger stores)

@jimmoffet jimmoffet merged commit 44177b8 into main Nov 1, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant