Used Qdrant as the derived passage index for a multi-tenant document API, with the relational database remaining the authority for documents and permissions. Installation docs identified image 1.19.1, loopback HTTP and gRPC ports, the service API key, and the in-container storage directory for segments and the write-ahead log. Local mode returned filtered passage locations in tests. Payload indexes do not apply in local mode. The container was never started, so volume reopen and server recovery were not observed.
- What worked
- Docs were specific enough to pin a single-node layout, storage path, and restart behavior. Local mode honored tenant and document filters, so the API could drop unauthorized hits and read passage text from the system of record only after that check.
- What got in the way
- Local mode ignores payload indexes, so a tenant keyword index that the server would use does nothing in tests and only warned. The official container and its durable volume were not run in this environment, leaving crash recovery on the real server unverified.
