SearchBuilder
DSL for search (/points/query). Provide a query (vector, id, fusion, order-by, sample) and/or one or more prefetch sub-requests, plus a positive limit.
Properties
Stable token sent as X-Qdrant-Route-Affinity, so reads carrying the same one are served by the same replica: a user id, a session id, a hashed api key. The thing that should be sticky is one reader's session rather than the whole application, which is why this is per request and not on the client.
Drop hits scoring below this threshold.
Which payload to return (defaults to the server's behavior).
Whether to return the stored vectors.
Functions
Context search: steer results by positive/negative example pairs, without a target.
Guided (discovery) search: rank by a target, constrained by context example pairs.
Look up query-by-id vectors from another collection.
Tune the accuracy/speed trade-off.
Add a prefetch sub-request (repeatable; prefetches may nest for multi-stage retrieval).
Search by the stored vector of an existing point (a "more like this" query).
Set the query directly (e.g. a prebuilt QueryInterface).
Search by an explicit dense query vector.
Search by text the server embeds with model, instead of by a vector the caller computed. Needs a Qdrant with an inference provider configured. See InferenceInput.
Search by a multi-vector / late-interaction (ColBERT) query.
Recommend points close to positive examples and far from negative ones.
Rerank an original query from scored relevance feedback supplied by a downstream evaluator.