Skip to content

feat: Qdrant vector search backend #138

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+335 −51
Open

feat: Qdrant vector search backend #138

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 25 additions & 4 deletions docs/src/content/docs/core-concepts/semantic-search.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,13 +3,13 @@ title: Semantic Searching
---
import { Aside } from '@astrojs/starlight/components';

Semantic search allows you to find code based on meaning rather than just keywords. Kit supports semantic code search using vector embeddings and ChromaDB (both local and cloud), enabling you to search for code using natural language queries.
Semantic search allows you to find code based on meaning rather than just keywords. Kit supports semantic code search using vector embeddings with multiple vector database backends: ChromaDB (both local and cloud) and Qdrant, enabling you to search for code using natural language queries.

## How it works

- Chunks your codebase (by symbols or lines)
- Embeds each chunk using your chosen model (OpenAI, HuggingFace, etc)
- Stores embeddings in a local ChromaDB vector database
- Stores embeddings in a vector database (ChromaDB or Qdrant)
- Lets you search for code using natural language or code-like queries

## Quick Start
Expand Down Expand Up @@ -249,9 +249,30 @@ To migrate from cloud to local:
1. Unset `KIT_USE_CHROMA_CLOUD`
2. Rebuild your indexes locally

#### Other Backends
#### Qdrant (Alternative Backend)

While the `VectorDBBackend` interface is designed to support other vector databases, ChromaDB (local and cloud) is the primary focus for now. If you need other backends like Faiss, please raise an issue on the kit GitHub repository.
Kit also supports [Qdrant](https://qdrant.tech/), a open-source, high-performance vector search engine that can be run locally or as a managed service.

##### Prerequisites

- Qdrant client library (`pip install qdrant-client`)
- Python 3.10+
- Qdrant server (local or remote)

##### Configuration

Set the following environment variables to use Qdrant:

```bash
# Required: Enable Qdrant backend
export KIT_VECTOR_BACKEND="qdrant"

# Optional: Remote Qdrant instance (defaults to local)
export QDRANT_URL="http://localhost:6333"

# Optional: API key for remote instances
export QDRANT_API_KEY="your-api-key"
```

## Usage Patterns

Expand Down
Loading