Shared Vector Store Adapter (Qdrant) — Extraction

[Michaelzag]

Shared Vector Store Adapter (Qdrant) — Extraction

Related GitHub Issue

Refs: #6223

Note: This PR does not close #6223. It partially addresses the requested "vector database adapter" work by extracting a shared adapter module and providing the Qdrant implementation. Follow‑up PRs can extend this adapter as needed. No additional vector store implementations are included here.

Description

This PR extracts Qdrant vector‑store logic from Code Index into a shared, provider‑agnostic adapter. It keeps Code Index behavior the same, generalizes settings labels from “Qdrant …” to “Vector Database …”, and removes the legacy client after verifying tests.

Key implementation points:

• New shared adapter module under src/services/vector-store/:
  • interfaces.ts: VectorDatabaseAdapter, VectorRecord, VectorFilter, DatabaseCapabilities, VectorStoreConfig.
  • errors.ts: adapter‑level error taxonomy.
  • filters.ts: FilterTranslator + QdrantFilterTranslator (directory prefix, delete filters via pathSegments.*).
  • collection-manager.ts: ensure‑once cache per collection:dimension.
  • adapters/qdrant.ts: QdrantAdapter with URL/port normalization, ensure + dimension mismatch recreate, payload index creation, upsert shaping, search, delete‑by‑filter.
  • factory.ts: VectorStoreFactory.create() (Qdrant only for now).
• Code Index integration:
  • src/services/code-index/vector-store-adapter.ts: wrapper implementing IVectorStore by delegating to shared adapter; preserves parity and no‑op delete when collection missing.
  • src/services/code-index/service-factory.ts: switches to shared factory + wrapper; preserves config and dimension resolution.
• UI: generalized i18n labels to “Vector Database URL/API Key” across all locales (no config schema changes).
• Removed legacy files: src/services/code-index/vector-store/qdrant-client.ts and its tests.
• Optional collection isolation: an optional collectionSuffix is supported; default behavior is unchanged.

Compatibility

• No breaking changes. Code Index continues to work with the same configuration and data.
• Collection naming remains stable; an optional suffix is available for isolated collections when required. (Conversation Memory #7537 will use this)

Test Procedure

• Contract tests cover ensure, upsert/search, filter translation, and delete‑by‑filter.
• Qdrant adapter tests cover URL/port handling, payload index creation, and collection suffix.
• Wrapper tests cover directory‑prefix filters and delete‑by‑paths behavior.
• Full repo type‑check, lint, and tests are green.

Pre-Submission Checklist

• Issue Linked
• Scope limited to the linked issue
• Self-Review performed
• Tests updated/added
• Documentation impact considered
• Read and agree to CONTRIBUTING

Screenshots / Videos

Follow‑ups

• Conversation Memory can use this adapter with a collection suffix and a KV filter translator (separate PR) without touching Code Index. (yay!)

---

Important

Extracts Qdrant vector-store logic into a shared adapter module, updates Code Index integration, and generalizes UI labels.

• Behavior:
  • Extracts Qdrant vector-store logic into a shared adapter module under src/services/vector-store/.
  • Generalizes settings labels from "Qdrant ..." to "Vector Database ...".
  • Removes qdrant-client.ts and its tests from src/services/code-index/vector-store/.
• Adapter Module:
  • Adds interfaces.ts, errors.ts, filters.ts, collection-manager.ts, adapters/qdrant.ts, and factory.ts.
  • Implements QdrantAdapter with URL/port normalization, collection management, and CRUD operations.
• Code Index Integration:
  • Updates vector-store-adapter.ts to use the shared adapter.
  • Modifies service-factory.ts to switch to the shared factory and adapter.
• UI:
  • Updates i18n labels to "Vector Database URL/API Key" across all locales.
• Testing:
  • Adds contract tests for adapter operations.
  • Updates existing tests to reflect the new adapter structure.

^{This description was created by for b63ebfb. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

Thank you for this well-structured refactoring! The extraction of Qdrant vector store logic into a shared, provider-agnostic adapter pattern is clean and maintains backward compatibility while setting up a solid foundation for future vector database integrations.

Positive aspects:
✅ Clean separation of concerns with the adapter pattern
✅ Maintains backward compatibility - no breaking changes
✅ Good test coverage with contract tests, unit tests, and integration tests
✅ Proper error handling with custom error taxonomy
✅ Smart collection management with ensure-once caching
✅ Thoughtful i18n updates generalizing from "Qdrant" to "Vector Database"

I've left some suggestions inline that could improve the implementation further, but overall this is a solid architectural improvement that aligns well with the incremental approach requested in issue #6223.

[Michaelzag]

I'll address those roomote suggestions. Heading home for the day so it will likely be over the weekend or Tuesday.

[hannesrudolph]

@Michaelzag you still on this?

[Michaelzag]

Ya the pr is waiting