Closed marygriffus closed 6 months ago
Hey @marygriffus,
QdrantDocumentStore
creates an opinionated Qdrant collection, which is meant to work well with Haystack.
The best way to use it is to create a new Document Store and then continue using it via Haystack. If you already have a Qdrant collection, you should probably need to manually migrate it.
Resources:
I'm closing this issue. Feel free to reopen it if something is unclear or does not work.
Describe the bug When creating a QdrantDocumentStore, if there is already a preexisting qdrant instance with data in it, and the params do not match precisely,
recreate_index
will destroy the old index and create a new one, blowing away the old data and making it so that incoming data does not match. Even after turning this off and updating settings to match our Qdrant params, I ran into an issue that seemed to be a mismatch between the QdrantDocumentStore and the QdrantClient.To Reproduce Bring up a qdrant instance and start a collection with the config:
Then instantiate a QdrantDocumentStore like below and use it in a pipeline.
At first, I had
recreate_index=True
and left embedding_dim and hnsw_config blank, which blew my collection away and any new data failed to be added; ideally I think the document store would default to the settings discovered through the qdrant client. However, when I switched torecreate_index=False
, I continued to have issues.The first error I ran into with this setup was this:
I overrode those lines in
_set_up_collection
with these:and I then instead got this error:
From the context I would expect this to be an issue with the embedding model, but there is no method to add the embedding model to the document store, so I might be misunderstanding.
Describe your environment (please complete the following information):