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.
Many workflows want the ability to produce, store and search on embeddings.
This PR attempts to fit in that workflow by taking advantage of the postgres pgvector storage and search. This is a little experimental, frameworks like FAISS provide really fancy math for the creation and search of embeddings. But doing it in pgvector first gives us something to work with and evaluate.
This PR adds rest endpoint for storing and retrieving embeddings (because GraphQL requires json for data) and to be honest, right now for ease, the embeddings are in in json too. But in the future we can come up with a more efficient serialization strategy (probably involving numpy).
This also adds search for entities based on embeddings. This part is added to GraphQL.
There is also an
embedding_modelstable where we can store information about which model each embedding is from, and match that to a URL in a service like MLFlow.