[BUG] Bad request: Index required but not found for \"type\" of one of the following types: [keyword] code indexing

[rossdonald]

Problem (one or two sentences)

When using the codebase_search tool, the following error comes up when using a Qdrant hosted instance.

Bad request: Index required but not found for "type" of one of the following types: [keyword]. Help: Create an index for this key or use a different filter.

Seems related to recent change #8588

Context (who is affected and when)

Happens when trying to use codebase_search tool with qdrant

Reproduction steps

Windows, VSCode latest, Roo Code v3.29.4
Ask roo to use codebase_search with existing index in qdrant

Expected result

codebase_search returns results without error

Actual result

Error bad request

Variations tried (optional)

Tried deleting index and recreating but same result

App Version

v3.29.4

API Provider (optional)

None

Model Used (optional)

Kimi k2, glm 4.6

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

**Assistant:**
I'll help you find the parts of the code related to chunking. Let me start by searching for chunking-related code across the codebase.

<codebase_search>
<query>chunking chunker document chunking</query>
</codebase_search>

---

**User:**

[codebase_search for 'chunking chunker document chunking'] Result:
The tool execution failed with the following error:
<error>
Error codebase_search: {"headers":{},"url":"https://myid123.us-west-1-0.aws.cloud.qdrant.io/collections/ws-a1e0a0eada56aeec/points/query","status":400,"statusText":"Bad Request","data":{"status":{"error":"Bad request: Index required but not found for \"type\" of one of the following types: [keyword]. Help: Create an index for this key or use a different filter."},"time":0.000025829},"name":"Error","message":"Bad Request","stack":"Error: Bad Request\n    at Object.e [as queryPoints] (c:\\Users\\user\\.vscode\\extensions\\node_modules\\.pnpm\\@qdrant+openapi-typescript-fetch@1.2.6\\node_modules\\@qdrant\\openapi-typescript-fetch\\dist\\esm\\fetcher.js:169:23)\n    at processTicksAndRejections (node:internal/process/task_queues:105:5)\n    at Ire.query (c:\\Users\\user\\.vscode\\extensions\\node_modules\\.pnpm\\@qdrant+js-client-rest@1.14.0_typescript@5.8.3\\node_modules\\@qdrant\\js-client-rest\\dist\\esm\\qdrant-client.js:1406:26)\n    at mZe.search (c:\\Users\\user\\.vscode\\extensions\\rooveterinaryinc.roo-cline-3.29.4\\services\\code-index\\vector-store\\qdrant-client.ts:443:28)\n    at QZe.searchIndex (c:\\Users\\user\\.vscode\\extensions\\rooveterinaryinc.roo-cline-3.29.4\\services\\code-index\\search-service.ts:58:20)\n    at AXi (c:\\Users\\user\\.vscode\\extensions\\rooveterinaryinc.roo-cline-3.29.4\\core\\tools\\codebaseSearchTool.ts:85:52)\n    at ude (c:\\Users\\user\\.vscode\\extensions\\rooveterinaryinc.roo-cline-3.29.4\\core\\assistant-message\\presentAssistantMessage.ts:486:6)"}
</error>

[roomote]

I'm exploring a potential fix for the Qdrant index issue and will open a PR to share progress

[roomote]

Opened a PR with my attempt at addressing this issue: #8964

The fix adds a keyword index for the "type" field in Qdrant to resolve the "Index required but not found" error. All tests are passing and CI checks have completed successfully. Feedback welcome!