Find answers from the community

Updated 6 months ago

milvus issues retrieving from existing store

At a glance

The community member is having issues with Milvus, where it seems to be deleting the recently indexed documents. The community members suggest that the issue might be related to the overwrite setting when initializing the MilvusVectorStore. They recommend trying to set overwrite to false to see if that resolves the issue. One community member also shares a gist with relevant Milvus logs.

Useful resources

tthoraxe

sooooo i'm not sure what i'm doing wrong here with Milvus, but it seems like it just keeps throwing everything away that I recently indexed. if I index some documents, and then try to set up an index from that same vector store, i don't get any results

6 comments

tthoraxe

gist incoming

tthoraxe

i see this in the milvus logs:

Plain Text

[2024/03/08 15:01:25.203 +00:00] [INFO] [datacoord/index_service.go:629] ["receive DropIndex request"] [traceID=83f20936f28c458523627ab370f1f6d6] [collectionID=448242123018748250] [partitionIDs="[]"] [indexName=] ["drop all indexes"=true]

tthoraxe

https://gist.github.com/thoraxe/7f54b5ae756b5362b3ec0871b845eeac

tthoraxe

looks like it was the overwrite=true

tthoraxe

when initializing MilvusVectorStore it seems like the overwrite setting causes the existing collection to be deleted, maybe.

LLogan M

Yea try setting overwrite to false

Add a reply