Package-level declarations
Types
One alias→collection mapping, as returned by listAliases / listCollectionAliases.
A single change applied by updateAliases. All operations in one call are applied atomically, which is what makes a zero-downtime reindex possible (build a new collection, then swap the alias).
A collection's name, as returned by listCollections.
Summary of a collection returned by getCollection.
Optimization/health status of a collection. Unrecognized values (from a newer server) decode to UNKNOWN rather than failing the whole response.
A single filter condition. Most conditions target a payload Field with a FieldMatcher; the rest cover Qdrant's special conditions (is_empty, is_null, has_id, has_vector, nested) and recursive nesting of a whole Filter via Sub.
A positive/negative example pair for discovery and context search.
Request body for PUT /collections/{name}.
Selects which points a delete targets: an explicit id list or a filter.
Sort direction for QueryInterface.OrderBy.
A distinct value of a faceted payload key together with how many points carry it. Returned by facet, ordered by descending count.
A facet value: Qdrant returns a payload key's distinct values as a string, integer, or boolean.
The matcher applied to a payload field inside a Condition.Field. Each variant maps to exactly one Qdrant condition block (match, range, values_count, geo_*), mirroring the Qdrant filter model.
A Qdrant filter: four independent, combinable clauses. Each holds a list of Conditions and clauses can nest recursively (a condition can itself be a whole Filter — see Condition.Sub), so any boolean expression is expressible.
Fusion algorithm combining the results of several Prefetch sources.
HNSW index tuning. All fields are optional; omitted ones fall back to Qdrant's defaults. Can be set collection-wide or overridden per named vector.
Where to look up a point's vector for SearchRequest.lookupFrom: a collection and optional vector name.
How multi-vectors are compared.
Config enabling multi-vector (late-interaction / ColBERT) storage on a dense vector.
Optimizer tuning for a collection. All fields are optional; on create, omitted ones use Qdrant's defaults; on update, omitted ones keep the current value.
A point payload: an arbitrary JSON object with heterogeneous values (strings, numbers, booleans, arrays, nested objects). Kept as a JsonObject rather than a fixed schema, since Qdrant payloads are schemaless; typed access is left to the caller.
Payload field index type for createPayloadIndex. Indexing a field makes filtering on it scale.
A group of hits sharing the same group_by value, returned by searchGroups.
A Qdrant point identifier. Qdrant accepts exactly two forms: an unsigned 64-bit integer or a UUID string. Modelled as a sealed type so the two cases are impossible to confuse.
A point's id and the vector(s) to write, for updateVectors.
A prefetch sub-request: candidates fetched first, then combined or reranked by the outer SearchRequest.query. Prefetches nest recursively for multi-stage retrieval.
The query of a /points/query request: what to do with the (optionally prefetched) candidates.
How QueryInterface.Recommend uses positive/negative examples. Default (null) is average-vector.
A point returned by scroll (no similarity score).
A search hit: a point with its similarity score.
One page of scroll results plus the cursor to the next page.
Request body for a single POST /collections/{name}/points/scroll page.
Request body for POST /collections/{name}/points/query/groups.
Distance matrix in pairs form: an explicit list of scored point pairs.
Fine-tuning for a search's accuracy/speed trade-off.
Request body for POST /collections/{name}/points/query.
Metadata for one snapshot, returned by the create and list operations.
Source-of-truth policy when recovering a snapshot into a collection that has replicas. Ignored for a single-replica collection.
Config for a named sparse vector under CreateCollectionRequest.sparseVectors.
Request body for PATCH /collections/{name} — tune an existing collection's config.
The vector(s) attached to a point, in any shape Qdrant accepts or returns:
Storage datatype for vector elements. Defaults to FLOAT32 server-side when omitted.
A bare vector input — usable directly as a nearest-search QueryInterface and as a positive/negative example inside QueryInterface.Recommend, QueryInterface.Discover and ContextPair. One of a dense QueryInterface.Vector, a stored-point QueryInterface.ById, a QueryInterface.Sparse, or a QueryInterface.MultiVector.
Configuration for a single (dense) vector: dimensionality, metric, and storage options.
The vectors config of a collection, which Qdrant represents in two shapes:
Payload projection for search/scroll results. Qdrant accepts four wire shapes: