Initial vector db implementation #335
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SmittieC
reviewed
Mar 25, 2024
SmittieC
reviewed
Mar 25, 2024
available_variables should be added as "source_material" using form_data , but I could not figure out how to od it with form_data.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This adds a vector DB implementation based off langchain pgvector but backed by a custom Django model.
This can not be merged to main yet since our current production DB does not support the pgvector extension.
Upgrade note
If you want to update without loosing all your existing data in postgres you can follow the instructions here: https://gist.github.com/snopoke/80e9a2e88ec493b7d4efae2578339f00