Kdrant
Entry point: creates a QdrantClient backed by the REST/Ktor engine.
Kdrant(host = "localhost", port = 6333) {
apiKey = "test-key"
requestTimeout = 5.seconds
}.use { qdrant ->
qdrant.createCollection("docs") { vector { size = 768; distance = Distance.COSINE } }
}Parameters
defaults to 6333 (Qdrant's REST port; gRPC's 6334 is not used by this engine).
maximum points per upsert request; larger batches are split automatically.
soft cap on an upsert batch's serialized size, so the ~32 MiB REST payload limit is respected even for high-dimensional vectors. A batch is also split when it reaches upsertBatchSize points, whichever comes first.
when non-null, installs request/response logging at this level with the api-key header redacted so the key never reaches the logs. null (default) disables logging.
how many connections the pool keeps open to the Qdrant host; null (default) keeps the engine's. These are engine settings, not connection settings, which is why they live here rather than on dev.kdrant.KdrantConfig — that stays transport-neutral. Applied by the JVM engine; the native engines do not expose a pool and ignore them.
how long an idle pooled connection is kept; null (default) keeps the engine's. Applied by the JVM engine, ignored by the native ones.
called once per request for the value of an X-Request-Id header, so a call can be followed into Qdrant's logs. null (default) sends no header. Return your own trace id to tie the two together, or { UUID.randomUUID().toString() } for a standalone one.
an escape hatch applied last to the underlying Ktor HttpClientConfig — install your own plugins (metrics, tracing) or override any default Kdrant set. Runs after Kdrant's own setup, so it wins.
wraps the engine before the client is built, for anything that belongs above the wire rather than inside it. kdrant-otel's kdrantTracing(...) is one; a caching or rate-limiting decorator of your own is another. The default returns the engine untouched.