-
Notifications
You must be signed in to change notification settings - Fork 126
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
[Integration] Request to support FAISSDocumentStore in 2.x #717
Comments
Hi @v3ss0n and thanks for the feature request. Do you envision an exact porting of the FAISS document store from Haystack 1.x, with the accompanying persistent storage, or would an in-memory, pure-FAISS solution also work? |
Exact porting is not necessary as long as we can use Fiass as DS , and yes of-course we are looking forward for both persistant and and in-memory DS but whatever work first. |
I think having in-memory, basic support for FAISS can be done rather easily. |
yeah i agree , sqlite store was a mess and hard to manage. Lets start with in-memory. |
Hi FAISS is more important then you might give it credit for, it is necessary for Haystack to move FAISS support to version 2. One of the most important attributes I like about FAISS That it uses local files and for document store, it can use SQL lite, This is a great advantage when we have small but many different isolated databases it may not be very scalable but there is a case to be made for small number of users requiring specialized RAG type applications. |
Would be very useful to have FAISS support in Haystack 2.0! |
Is your feature request related to a problem? Please describe.
We are having problem migrating current version to 2.0 due to no FAISSSupport
Describe the solution you'd like
Due to is simplicity , performance and developer experience , we and many other RAG solution provider are now using FAISS . So it would be nice to integrate it.
Describe alternatives you've considered
QDrant and many others are not approved by some organization yet because they are very new and not backed by big vendors.
The text was updated successfully, but these errors were encountered: