You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 18, 2024. It is now read-only.
It would be nice to be able to use a consistent corpus of raw data (like what gets stored in Mongo) and use different models and techniques to easily generate vector embeddings on that data that could all be store in Postgres together, and selectively queried.
Some ideas.
Separate tables or separate columns or even separate databases for the different embeddings, each legibly-labeled.
The ability to choose which model's embbeddings are being queried from the API. Could be an env var that's set at start up of the backend API, or an optional parameter passed to the API.
The text was updated successfully, but these errors were encountered:
It would be nice to be able to use a consistent corpus of raw data (like what gets stored in Mongo) and use different models and techniques to easily generate vector embeddings on that data that could all be store in Postgres together, and selectively queried.
Some ideas.
The text was updated successfully, but these errors were encountered: