[Bug]: [Nightly] Expected to search 9 results out of 10 but failed

[NicoYuan1986]

Is there an existing issue for this?

• I have searched the existing issues

Environment

- Milvus version: 2710eb3(2.5)
- Deployment mode(standalone or cluster):cluster
- MQ type(rocksmq, pulsar or kafka):    kafka
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

Expected to search 9 results out of 10 but failed.

2025-03-19T19:28:03Z {container="step-test"} @pytest.mark.tags(CaseLabel.L2)
2025-03-19T19:28:03Z {container="step-test"} def test_range_search_radius_range_filter_not_in_params(self):
2025-03-19T19:28:03Z {container="step-test"} """
2025-03-19T19:28:03Z {container="step-test"} target: test range search radius and range filter not in params
2025-03-19T19:28:03Z {container="step-test"} method: create connection, collection, insert and search
2025-03-19T19:28:03Z {container="step-test"} expected: search successfully as normal search
2025-03-19T19:28:03Z {container="step-test"} """
2025-03-19T19:28:03Z {container="step-test"} # 1. initialize with data
2025-03-19T19:28:03Z {container="step-test"} collection_w, _vectors, _, insert_ids, time_stamp = self.init_collection_general(
2025-03-19T19:28:03Z {container="step-test"} prefix, True, nb=10)[0:5]
2025-03-19T19:28:03Z {container="step-test"} # 2. get vectors that inserted into collection
2025-03-19T19:28:03Z {container="step-test"} vectors = np.array(_vectors[0]).tolist()
2025-03-19T19:28:03Z {container="step-test"} vectors = [vectors[i][-1] for i in range(default_nq)]
2025-03-19T19:28:03Z {container="step-test"} # 3. range search with L2
2025-03-19T19:28:03Z {container="step-test"} range_search_params = {"metric_type": "COSINE",
2025-03-19T19:28:03Z {container="step-test"} "radius": 0, "range_filter": 1}
2025-03-19T19:28:03Z {container="step-test"} >       collection_w.search(vectors[:default_nq], default_search_field,
2025-03-19T19:28:03Z {container="step-test"} range_search_params, default_limit,
2025-03-19T19:28:03Z {container="step-test"} default_search_exp,
2025-03-19T19:28:03Z {container="step-test"} check_task=CheckTasks.check_search_results,
2025-03-19T19:28:03Z {container="step-test"} check_items={"nq": default_nq,
2025-03-19T19:28:03Z {container="step-test"} "ids": insert_ids,
2025-03-19T19:28:03Z {container="step-test"} "limit": default_limit})

2025-03-19T19:28:03Z {container="step-test"} [2025-03-19 18:37:32 - INFO - ci_test]: search_results_check: Numbers of query searched is correct (func_check.py:372)
2025-03-19T19:28:03Z {container="step-test"} [2025-03-19 18:37:32 - ERROR - ci_test]: search_results_check: limit(topK) searched (9) is not equal with expected (10) (func_check.py:387)

There are only 10 data in the collection, so Brute-force search should return all results.

Expected Behavior

pass

Steps To Reproduce

Milvus Log

https://jenkins.milvus.io:18080/blue/organizations/jenkins/Milvus%20Nightly%20CI(new)/detail/2.5/99/pipeline/144/

Anything else?

No response

[dosubot]

I found a similar open issue titled "[Bug]: Value returned does match Limits" on the Milvus GitHub repository. However, no solution has been found in the comments of that issue ^[1].

Regarding your current issue, it seems that the discrepancy in the number of search results could be related to how Milvus handles range search parameters, specifically 'radius' and 'range_filter'. When using the 'COSINE' metric type, the condition for filtering results is radius < distance <= range_filter. If these parameters are not set correctly, it might affect the number of results returned ^[2][3].

Additionally, discrepancies in search results can also occur due to duplicate Primary Keys (PKs) in different segments of your collection, or due to concurrent insert and delete operations in a Milvus cluster deployment. These issues have been noted in other contexts and might be relevant to your situation ^[4][5].

You might want to verify the configuration of your search parameters and check for any potential issues with duplicate PKs or concurrent operations that could affect the search results.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[yanliang567]

/assign @liliu-z
i guess it is about the range search, please help to assign
/unassign

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.