Get desktop application:
View/edit binary Protocol Buffers messages
CollectionsService manages the collections of a qdrant serverless space. Unlike the qdrant server API, it exposes only a simplified configuration: the manager turns it into concrete qdrant settings, which are never exposed to the tenant.
Creates a collection with the given tenant-facing configuration.
Every request names the collection by its tenant-facing name only. The tenant (`x-account-id`, `x-space-id`) travels in gRPC metadata, injected by auth. The storage id is the manager's: minted on create, resolved internally on get/delete.
Tenant-facing name of the collection to create.
The collection's configuration.
Result of a create.
Tenant-facing name of the collection.
Outcome, e.g. "created", "already exists".
Time spent to process
Deletes a collection and all of its data.
Names the collection to delete.
Tenant-facing name of the collection to delete.
Result of a delete.
Whether the collection existed and was deleted.
Time spent to process
Returns a single collection's configuration and stats.
Names the collection to fetch.
Tenant-facing name of the collection.
The collection's configuration and stats, if it exists.
Whether the collection exists.
The configuration the collection was created with.
Available points as of the last applied write (eventually consistent); absent until the updater has written stats for the collection.
Time spent to process
Lists the caller's collections.
Lists the caller's collections. The tenant travels in metadata.
Maximum number of collections to return. Defaults to 20 and must not exceed 100.
Opaque token returned as `next_offset_token` by the previous page. Clients must not interpret this value.
The caller's collections.
Collections in this page.
Opaque token to pass as `offset_token` to retrieve the next page. Absent when there are no more results.
Time spent to process
Exact match on booleans, e.g. `is_active: true`.
Used in:
(message has no fields)
The tenant's collection config. Persisted verbatim. At least one dense or sparse vector is required.
Used in: ,
Keyed by vector name. The empty name "" is the unnamed default vector, as in qdrant; a collection either has the single unnamed vector or named ones.
Keyed by vector name.
Keyed by payload field name (JSON path, e.g. `user_id` or `meta.tags`).
One collection in a listing.
Used in:
Tenant-facing name of the collection.
Available points as of the last applied write (eventually consistent); absent until the updater has written stats for the collection.
Range filters on RFC 3339 datetimes, e.g. `created_at: "2023-02-08T10:49:00Z"`.
Used in:
(message has no fields)
Configuration of a single dense (embedding) vector.
Used in:
Dimensionality of the embedding, e.g. 512 (CLIP), 1536, 3072.
Distance metric used to compare vectors.
Store several sub-vectors per point and compare with max-sim, for late-interaction models (ColBERT, ColPali, ...).
Precision/cost trade-off for this vector. Unset: HIGH.
Explicitly disable stemming (overrides any language default).
Used in:
(message has no fields)
Distance metric used to compare dense vectors.
Used in:
Unset; a concrete metric is required.
Cosine similarity.
Euclidean (L2) distance.
Dot product.
Manhattan (L1) distance.
Range filters on floating point (and integer) numbers, e.g. `price: 99.5`.
Used in:
(message has no fields)
Geo radius / bounding box / polygon filters on `{lon, lat}` values.
Used in:
(message has no fields)
Exact match and/or range filters on integers, e.g. `age: 25`. Both are on by default; turning one off shrinks the index.
Used in:
Support exact-match filters.
Support range filters.
Exact match on string values, e.g. `color: "red"`.
Used in:
If set, enable prefix matching (`match: { "prefix": ... }`) on this field. Presence of this message enables prefix matching; it has no options yet.
Prefix matching options for the keyword index. Has no options yet: presence of this message enables prefix matching.
Used in:
(message has no fields)
One payload index. Only the *kind* of filter the field supports is chosen here; storage placement of the index is the manager's decision.
Used in:
The kind of filter the field supports.
Exact match on strings.
Exact match and/or range filters on integers.
Range filters on numbers.
Exact match on UUIDs.
Range filters on datetimes.
Full-text filtering.
Geo filters.
Exact match on booleans.
How much of the original vector precision may be traded for cost. The manager turns this into a concrete quantization / datatype choice; the tenant never picks scalar/product/binary quantization or its parameters directly.
Used in: ,
Unset: HIGH.
Aggressive compression, lowest cost, approximate results.
Moderate compression with a small accuracy trade-off.
Light compression, near-exact results.
No lossy compression: exact vectors, fully in memory. Highest cost.
Snowball stemming for a full-text index.
Used in:
Language for the snowball algorithm, e.g. "english".
Configuration of a single sparse vector.
Used in:
Apply the IDF modifier at query time. Enable for BM25-style models that expect inverse-document-frequency weighting.
Precision/cost trade-off for this vector. Unset: HIGH.
Stemming algorithm for a full-text index. Unset: no stemming.
Used in:
Which stemming algorithm to use.
Snowball stemmer for the given language.
Explicitly disable stemming.
Tokens ignored by a full-text index. Language names match qdrant (e.g. "english"); predefined lists and custom tokens are merged.
Used in:
Languages whose predefined stopword lists to apply.
Extra stopwords to ignore, merged with the language lists.
Full-text filtering on string values.
Used in:
Tokenizer to split text with. Unset: WHITESPACE.
Lowercase text before indexing. Default true.
Support phrase queries; extra index structure. Default true.
Minimum token length to index.
Maximum token length to index.
Fold accented characters to ASCII. Default false.
Tokens to ignore at index and query time.
Stemming algorithm. Unset: engine default (no stemming).
Full-text tokenizer, mirrors qdrant's `TokenizerType`.
Used in:
Unset: WHITESPACE.
Index every prefix of each token.
Split on whitespace.
Split on word boundaries.
Language-aware tokenization.
Exact match on UUID strings; like keyword but stored compactly.
Used in:
(message has no fields)