[vector store 12/13] Let a deployment tune a Qdrant collection's HNSW, optimizers and quantization (speedkick)

[edwinyyyu]

Purpose of the change

Lets a deployment tune the HNSW index, the optimizers and the quantization of a Qdrant collection. Split out of #1606 on review, since it is a tangential change to the store-as-collection work; it comes over from default (a0753d3).

Stack

Slice 12 of 13, every PR targeting speedkick; merge bottom-up.

#	PR	change
1	#1606 (merged)	Remove per-project filterable properties
2	#1597	Add session, source and expansion to EventMemory
3	#1622	Create a session's storage with the session, never on a request
4	#1623	Make the examples that write to a project create it first
5	#1624	Make no memory request create a project
6	#1625	Remove open-or-create and close from both stores
7	#1626	Rename logical collection to partition, and open to get, on both stores
8	#1627	Make a vector store one collection, with string-keyed partitions
9	#1631	Mint an incarnation per partition life; delete logically, reclaim by purge
10	#1628	Make a vector store filter only on the properties it declares
11	#1630	Bound every request to a remote vector store by a configured timeout
12	#1618 (this PR)	Let a deployment tune a Qdrant collection's HNSW, optimizers and quantization
13	#1616	Close the filter union, and make negation the complement on every backend

This PR's own change is its last commit, f08d6a71 (6 files changed, 257 insertions(+), 9 deletions(-)); the rest of its diff is the slices under it, and drops out as they merge. Stacked on #1630; #1616 is stacked on it.

What changed

• QdrantConf gains hnsw_config, optimizers_config and quantization_config: plain mappings mirroring qdrant-client's HnswConfigDiff, OptimizersConfigDiff and QuantizationConfig (for example {"turbo": {"always_ram": true, "bits": "bits2"}}), so qdrant-client stays optional for configuration parsing. DatabaseManager passes them to QdrantVectorStoreParams, which validates them against qdrant's own models and reports a failure as a configuration error.
• They apply to the store's data collection, never to its registry collection.
• m must be 0 or unset: the collection is multi-tenant and disables the global graph in favor of per-partition payload indexing, so a deployment tunes payload_m. It defaults to 16, as before.

Tests

Plain mappings coerce to qdrant's models; m of 0 or unset is accepted and any other value is refused naming payload_m; the native HNSW config merges overrides and pins m at 0; the overrides reach the data collection's creation and not the registry's. Configuration parsing and the manager's wiring assert the three fields round-trip.

uv run pytest packages/server/server_tests packages/client/client_tests: 2375 passed, 2 skipped, on the slice-13 tree (2026-09-15, on #1597 tip 4149fd5); this tip passes its own run. ruff check, ruff format --check and ty check --project packages/server clean.

🤖 Generated with Claude Code

https://claude.ai/code/session_01ESpWYTmCR7X3bJEpoA8SAn