-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Semantic search is not working for MongoDBAtlasDocumentStore #6643
Comments
Hi @bilgeyucel, My issue was indeed the same, it looks like Haystack uses the old way to query Mongo with embeddings. With the latest MongoDB Atlas update there are two ways of searching with mongo:
I would love to see these two functions integrated, so the Sparse search for I fixed your issue with semantic search by changing the pipeline to the following, but this only works with the new VectorSearch index, this index is
|
Just checking if this issue is going to be updated for 1.x? It appears to simply be the pipeline jvollmuller-risk mentioned. I get 0 results with retriever from MongoDB Atlas currently. If I change the pipeline to the new search syntax and specify the search index (the index field, not the collection) it works, but in my environment I would be required to change this each time the instance spins up. |
Hi @scottroot, we're working on the issue right now. If you'd like to help out, feel free to submit a PR to fix it. Your contribution would speed up the resolution process! :) |
fixed by #6811 |
@julian-risch Should I create another issue for this? |
Describe the bug
EmbeddingRetriever doesn't return any results when used with MongoDBAtlasDocumentStore. The reason seems like MongoDBAtlasDocumentStore
Error message
No error
Expected behavior
Semantic search should be possible with EmbeddingRetriever
Additional context
There's no problem in
write_documents
,update_embeddings
andget_document_count()
methods ofMongoDBAtlasDocumentStore
. The code below works for InMemoryDocumentStore properly.Issue #6632 can be related to this issue.
To Reproduce
FAQ Check
System:
The text was updated successfully, but these errors were encountered: