#7495·mem0

TS SDK: Qdrant search fails with @qdrant/js-client-rest 1.19 (client.search removed)

Author: xulongwu4Created Sep 29, 2026Updated Sep 29, 2026
Labelssdk-typescriptvector-store

Summary

@qdrant/js-client-rest 1.19.0 removed the deprecated QdrantClient.search() (along with searchBatch, searchPointGroups, recommend*, discover*) in favour of the Query API. The TypeScript OSS Qdrant vector store still calls this.client.search(...) in Qdrant.search() (mem0-ts/src/oss/src/vector_stores/qdrant.ts), and the optional peer range ^1.18.0 admits 1.19.0.

Any fresh install that resolves the Qdrant client to 1.19.x fails on every semantic search, including the search that Memory.add() performs during extraction:

TypeError: this.client.search is not a function

Reproduction

  • [email protected] + @qdrant/[email protected], Qdrant server 1.19.1
  • Configure vectorStore: { provider: "qdrant", config: { url: "http://localhost:6333", ... } }
  • Call memory.add(...) or memory.search(...) → TypeError: this.client.search is not a function

Pinning the client to 1.18.0 makes it work again. keywordSearch() already uses client.query(), so only the dense path is affected.

Suggested fix

Use client.query(collection, { query: vector, filter, limit, with_payload: true }) and map response.points. The Query API is available across the whole supported peer range (^1.18.0).