[DEV-15246] - add generate embeddings command - #4746
Open
zachflanders-frb wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
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.
Description:
This is PR 3/3 for this feature. The first PR added the pgvector extension to the app, the second PR adds the EmbeddingMixin and the fields on the models that should have embeddings generated. This PR adds the django management command to generate these embeddings.
Technical Details:
These embeddings will potentially take several hours to generate, but will only need to be generated once. The embeddings are auto generated on object save or creation. The existing loaders (e.g. load_naics) will generate embeddings for new records created with get_or_create, but updated or bulk_update records bypass the save method and will need to be manually regenerated. If the embedding fails the save will continue without an exception being raised, so it will still work in the legacy aws environment if bedrock is not available.
Requirements for PR Merge:
Explain N/A in above checklist: