KdrantConfig
Resolved, immutable connection configuration for a Kdrant client.
Credentials
apiKey is the cluster's master key: full read and write over every collection. bearerToken is a Qdrant JWT, which carries claims that narrow it — read-only, a named collection, or a payload filter deciding which points the caller may see at all. Exactly one of the two, or neither.
A credential is refused over plaintext HTTP unless host is a loopback address, because a key sent in the clear across a network is a key someone else has. A request to 127.0.0.1 never reaches a network, which is why a local node with an API key needs no certificate.
Constructors
Properties
Qdrant JWT sent as Authorization: Bearer; mutually exclusive with apiKey.
timeout for establishing a connection; null uses the engine default.
dispatcher the client runs on; injectable for tests. The default is platform-dependent, see ioDispatcher.
how many times to retry a retryable failure (HTTP 429/502/503/504 and transient I/O errors) with exponential backoff + jitter. 0 disables retries.
per-request timeout (applies to each attempt).
base delay before the first retry; each subsequent retry backs off exponentially, capped at retryMaxDelay. The server's Retry-After is honored when present.
upper bound on a single retry delay.
maximum idle time between two data packets on an open connection; null uses the engine default.
which certificates TLS will accept. The default is the platform's own store; see TrustAnchors for what each platform reads and which options it can honour. Ignored when useTls is false, because there is no certificate to judge.