mirror of
https://github.com/qdrant/qdrant.git
synced 2026-08-01 15:40:53 -05:00
* Remove deprecated search/recommend/discover endpoints from OpenAPI Remove deprecated REST API endpoint definitions from the OpenAPI generator. These endpoints were deprecated in v1.13.3 (`f4ced2567`, #5907, 2025-01-30) in favor of the universal `/points/query` endpoint: - POST /points/search - POST /points/search/batch - POST /points/search/groups - POST /points/recommend - POST /points/recommend/batch - POST /points/recommend/groups - POST /points/discover - POST /points/discover/batch Also removes the corresponding request types from the schema generator and updates the expected API count in the consistency check. Co-authored-by: Cursor <cursoragent@cursor.com> * Migrate OpenAPI integration tests to /points/query The deprecated /points/search, /points/recommend and /points/discover endpoints (along with their /batch and /groups variants) were removed from the OpenAPI spec, which caused validation failures in the Python integration test harness. This commit migrates the affected tests to the universal /points/query endpoint: - Delete tests dedicated to the deprecated endpoints: test_recommend.py, test_discover.py, test_multicollection_reco.py, test_recommendation_multivector.py - Refactor remaining tests to call /points/query (and /query/batch, /query/groups), translating request bodies (vector -> query / using, positive/negative -> query.recommend, target/context -> query.discover) and unwrapping the new result.points response shape. - Drop equivalence assertions against the now-removed legacy endpoints. Co-authored-by: Cursor <cursoragent@cursor.com> * Relax non-empty assertions in migrated recommend/discover tests The previous migration added `len(...) > 0` assertions to tests that previously only checked equivalence between the deprecated and new API. These assertions are too strict because the parametrized `query_filter` cases legitimately produce empty result sets. Drop the `> 0` assertion and rely on `request_with_validation` to verify the response is well-formed and HTTP OK. Co-authored-by: Cursor <cursoragent@cursor.com> * Migrate remaining OpenAPI tests off deprecated search endpoints Tests added to dev after the original migration was written still call /points/search and /points/recommend/groups through `request_with_validation`, which resolves the endpoint against the OpenAPI spec and therefore breaks once the endpoint is not in the spec: - test_turbo4_storage.py, test_sparse_idf_corpus.py, test_validation.py: translate /points/search to /points/query (vector{name,vector} -> query + using, result -> result.points). - test_group.py: drop the /points/recommend/groups half of the lookup_from validation test in favour of the query equivalent. test_sparse_idf_corpus.py's test_query_api_supports_idf_corpus goes away: with the helper on /points/query every test in the file now exercises what it asserted. Also record why test_recommend_group cannot assert on its groups: it uses every point in the collection as a recommend example, so all of them are excluded and the result is legitimately empty. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * Regenerate openapi.json without the deprecated search endpoints Drops the 8 deprecated paths and the request schemas that only they referenced: Search/Recommend/Discover request (+Batch, +Groups) types and their exclusive dependencies (NamedVector, NamedSparseVector, NamedVectorStruct, UsingVector, RecommendExample, ContextExamplePair). Regenerated output is a strict subset of the previous spec, and every remaining $ref still resolves. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * Deprecate the search/recommend/discover RPCs in gRPC The REST counterparts have carried `deprecated: true` since v1.13.3 and are now gone from the OpenAPI spec, while the gRPC RPCs never got any deprecation annotation at all. Mark all 8 with `option deprecated = true` so generated clients warn, and point each doc comment at its `Query` replacement. tonic puts `#[deprecated]` on the generated client methods only; the server trait gets the doc comment alone, so our own `impl` is unaffected. The RPCs keep serving traffic — this is annotation only. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * Restore the deleted recommend/discover suites on /points/query The earlier migration deleted these four files outright, but the query-side tests it left behind are all shallow smoke tests (`len(result) > 0`, `"points" in result[0]`). The deleted ones carried invariants with no query-API equivalent anywhere, so deleting them was a real loss of coverage rather than de-duplication: - test_recommend.py: default strategy equals average_vector; batch results identical to sequential singles across six request shapes; best_score with only negatives yields all-negative scores; best_score with a single positive orders identically to a nearest query; raw vectors as examples equal ids as examples. - test_discover.py: context-only scores are all <= 0; target-only orders identically to a nearest query but scores differently; with a fixed context the integer part of the score is stable while the decimal part moves, and vice versa with a fixed target; batch equals singles; lookup_from by id equals by vector. - test_multicollection_reco.py: cross-collection lookup_from, plus wrong-vector-size, unknown-collection and unknown-vector rejections. - test_recommendation_multivector.py: the same recommend invariants over a max_sim multivector collection, which the query suite never covered. Only test_recommend_missing_lookup_from_collection_with_raw_vector is dropped as genuinely redundant — test_query.py's test_query_missing_lookup_from_collection covers query, query/batch and prefetch. Two request-shape differences the translation had to absorb: - Giving no examples at all is 422 (a RecommendInput validation rule), where the legacy API reported 400 from the query itself. A malformed example, such as an empty vector, is still 400. - DiscoverInput requires the `context` key and accepts only an explicit null to mean "no context", so target-only discover must spell it out. The legacy API let it be omitted. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
209 lines
6.4 KiB
Python
209 lines
6.4 KiB
Python
import pytest
|
|
|
|
from .helpers.collection_setup import drop_collection
|
|
from .helpers.helpers import request_with_validation
|
|
|
|
|
|
@pytest.fixture(autouse=True)
|
|
def setup(on_disk_vectors, collection_name):
|
|
multivector_collection_setup(collection_name=collection_name, on_disk_vectors=on_disk_vectors)
|
|
yield
|
|
drop_collection(collection_name=collection_name)
|
|
|
|
def multivector_collection_setup(
|
|
collection_name='test_collection',
|
|
on_disk_vectors=False):
|
|
drop_collection(collection_name=collection_name)
|
|
|
|
response = request_with_validation(
|
|
api='/collections/{collection_name}',
|
|
method="PUT",
|
|
path_params={'collection_name': collection_name},
|
|
body={
|
|
"vectors": {
|
|
"size": 2,
|
|
"distance": "Dot",
|
|
"on_disk": on_disk_vectors,
|
|
"multivector_config": {
|
|
"comparator": "max_sim"
|
|
}
|
|
},
|
|
}
|
|
)
|
|
assert response.ok
|
|
|
|
# batch upsert
|
|
response = request_with_validation(
|
|
api='/collections/{collection_name}/points',
|
|
method="PUT",
|
|
path_params={'collection_name': collection_name},
|
|
query_params={'wait': 'true'},
|
|
body={
|
|
"points": [
|
|
{
|
|
"id": 1,
|
|
"vector": [
|
|
[-1, 1],
|
|
[-2, 2],
|
|
[-3, 3]
|
|
]
|
|
|
|
},
|
|
{
|
|
"id": 2,
|
|
"vector": [
|
|
[-1.5, 1.5],
|
|
[-2.5, 2.5],
|
|
[-3.5, 3.5]
|
|
]
|
|
},
|
|
{
|
|
"id": 3,
|
|
"vector": [
|
|
[-1.7, 1.7],
|
|
[-2.7, 2.7],
|
|
[-3.7, 3.7]
|
|
]
|
|
},
|
|
]
|
|
}
|
|
)
|
|
assert response.ok
|
|
|
|
response = request_with_validation(
|
|
api='/collections/{collection_name}',
|
|
method="GET",
|
|
path_params={'collection_name': collection_name},
|
|
)
|
|
assert response.ok
|
|
|
|
def test_multi_default_is_avg_vector(collection_name):
|
|
examples = {
|
|
"positive": [[1, 2]],
|
|
"negative": [[3, 4]],
|
|
}
|
|
|
|
default_response = request_with_validation(
|
|
api="/collections/{collection_name}/points/query",
|
|
method="POST",
|
|
path_params={"collection_name": collection_name},
|
|
body={
|
|
"query": {"recommend": examples},
|
|
"params": {"exact": True},
|
|
"limit": 10,
|
|
},
|
|
)
|
|
assert default_response.ok
|
|
|
|
# we should only get 3 because we don't have more
|
|
assert len(default_response.json()["result"]["points"]) == 3
|
|
|
|
avg_response = request_with_validation(
|
|
api="/collections/{collection_name}/points/query",
|
|
method="POST",
|
|
path_params={"collection_name": collection_name},
|
|
body={
|
|
"query": {"recommend": {**examples, "strategy": "average_vector"}},
|
|
"params": {"exact": True},
|
|
"limit": 10,
|
|
},
|
|
)
|
|
assert avg_response.ok
|
|
assert len(avg_response.json()["result"]["points"]) == 3
|
|
|
|
assert default_response.json()["result"] == avg_response.json()["result"]
|
|
|
|
|
|
def test_multi_single_vs_batch(collection_name):
|
|
# Bunch of valid examples
|
|
params_list = [
|
|
{
|
|
"query": {"recommend": {"positive": [1], "negative": [3]}},
|
|
"limit": 1,
|
|
},
|
|
{
|
|
# no positive because it's optional with this strategy
|
|
"query": {"recommend": {"negative": [1, 2], "strategy": "best_score"}},
|
|
"params": {"exact": True},
|
|
"limit": 1,
|
|
},
|
|
{
|
|
"query": {"recommend": {"positive": [1], "negative": [], "strategy": "average_vector"}},
|
|
"params": {"exact": True},
|
|
"limit": 1,
|
|
},
|
|
]
|
|
|
|
batch_response = request_with_validation(
|
|
api="/collections/{collection_name}/points/query/batch",
|
|
method="POST",
|
|
path_params={"collection_name": collection_name},
|
|
body={"searches": params_list},
|
|
)
|
|
|
|
assert batch_response.ok
|
|
assert len(batch_response.json()["result"]) == len(params_list)
|
|
|
|
# Compare against sequential single searches
|
|
for i, params in enumerate(params_list):
|
|
single_response = request_with_validation(
|
|
api="/collections/{collection_name}/points/query",
|
|
method="POST",
|
|
path_params={"collection_name": collection_name},
|
|
body=params,
|
|
)
|
|
assert single_response.ok
|
|
assert single_response.json()["result"] == batch_response.json()["result"][i]
|
|
|
|
|
|
def test_multi_without_positives(collection_name):
|
|
def req_with_positives(positive, strategy=None):
|
|
recommend = {"positive": positive}
|
|
if strategy is not None:
|
|
recommend["strategy"] = strategy
|
|
|
|
return request_with_validation(
|
|
api="/collections/{collection_name}/points/query",
|
|
method="POST",
|
|
path_params={"collection_name": collection_name},
|
|
body={
|
|
"query": {"recommend": recommend},
|
|
"limit": 2,
|
|
},
|
|
)
|
|
|
|
# Assert this is valid
|
|
response = req_with_positives([[1, 2]])
|
|
assert response.ok
|
|
|
|
# But all these are not. An empty vector is a malformed example, rejected
|
|
# once the query runs...
|
|
response = req_with_positives([[]])
|
|
assert response.status_code == 400
|
|
|
|
response = req_with_positives([[]], "average_vector")
|
|
assert response.status_code == 400
|
|
|
|
# ...whereas no examples at all violates a `RecommendInput` validation rule
|
|
# and is rejected before that, hence 422.
|
|
response = req_with_positives([], "best_score")
|
|
assert response.status_code == 422
|
|
|
|
|
|
def test_multi_best_score_works_with_only_negatives(collection_name):
|
|
response = request_with_validation(
|
|
api="/collections/{collection_name}/points/query",
|
|
method="POST",
|
|
path_params={"collection_name": collection_name},
|
|
body={
|
|
"query": {"recommend": {"negative": [[1, 2]], "strategy": "best_score"}},
|
|
"limit": 5,
|
|
},
|
|
)
|
|
assert response.ok
|
|
assert len(response.json()["result"]["points"]) == 3
|
|
|
|
# All scores should be negative
|
|
for result in response.json()["result"]["points"]:
|
|
assert result["score"] < 0
|