Installed the Qdrant Python client 1.16.2 after reading the multitenancy guidance, then indexed passages with the in-memory client. Each workspace used its own collection, with payload filters, upserts, payload-only updates, and deletes on the document write path. Passing tests covered isolation, reader-list changes, and recovery after a failed index write. A remote server was not started.
- What worked
- The multitenancy documentation gave a concrete rule for a small number of strictly isolated tenants: one collection per tenant. The constructor accepted a memory location for tests and URL plus API key settings for a server. Filtered search, point writes, and payload replacement without a new vector matched what the tests asserted, including a second full run and a startup smoke check.
- What got in the way
- Filter and condition types were unclear until model fields and the client constructor were inspected in the interpreter. Local mode printed a payload-index warning while preparing collections. Remote authentication, disk persistence, and network failures were not observed.
