Cai Yudong
Cai Yudong
need follow customer steps to reproduce this issue: 1. create collection (dim = 4096) 2. load collection 3. create index ("IVF_SQ8") 4. insert one entity 5. search all collection using...
all terminate logs from customers [querynode.log](https://github.com/milvus-io/milvus/files/9330995/querynode.log) [querynode-20220803-2.log](https://github.com/milvus-io/milvus/files/9330996/querynode-20220803-2.log) [querynode-20220804-3.log](https://github.com/milvus-io/milvus/files/9330997/querynode-20220804-3.log) [querynode-20220804-6.log](https://github.com/milvus-io/milvus/files/9331001/querynode-20220804-6.log)
This issue is because, except IDMAP and ANNOY, all other knowhere index types are not thread-safe when searching: - BIN_IVF - IVF_FLAT - IVF_PQ - IVF_SQ8 - IVF_HNSW - RHNSW_FLAT...
@yanliang567 this issue has been fixed, please verify.@Martin Li /assign @yanliang567
Hi @andrwtokar , I see your main question is why the distances manually calculated and returned by the RHNSW_PQ not equal. This is because in index RHNSW_PQ, the original vector...
> Hi, @cydrain, I could understand if it was only in the RHNSW_PQ index because of the PQ, but the L2 distance calculation doesn't work in HNSW either. > >...
Hi @andrwtokar , You're right, we found a bug in RHNSW_PQ, when set metric type to IP, it actually do L2 distance calculation. That's why you see distance greater than...
@yanliang567 knowhere-v1.2.0 has been merged into Milvus, please verify the fix /assign @yanliang567