mirror of
https://github.com/qdrant/landing_page.git
synced 2026-10-06 11:28:31 +02:00
1a40961d62
* initial commit; fixed anchor links on internal docs pages * add back in absolute paths for links in code comments * fix: update linkchecker include filter to match server port 1314 PR #1629 changed the Hugo server to port 1314 but forgot to update the --include filter, which still matched port 1313. This caused all links to be excluded, making the checker a no-op (0 checked, 82277 excluded). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * Fix url rewrite regex so images are not impacted * Fix links from non-documentation pages * Fix broken links * more broken links * more broken links * broken link * Add srcset width descriptor to .lycheeignore * Ignore URLs that contain a % character * Anchor regex so it matches the entire URL --------- Co-authored-by: kanungle <neil.kanungo@gmail.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: Abdon Pijpelink <abdon.pijpelink@qdrant.com>
78 lines
2.8 KiB
Markdown
78 lines
2.8 KiB
Markdown
---
|
|
title: From Redis
|
|
weight: 70
|
|
---
|
|
|
|
# Migrate from Redis to Qdrant
|
|
|
|
## What You Need from Redis
|
|
|
|
- **Redis address** — host and port of your Redis instance
|
|
- **FT index name** — the RediSearch full-text index that contains your vectors
|
|
- **Authentication** — username and password, if configured
|
|
|
|
<aside role="alert"><strong>Important:</strong> Redis does not expose vector configurations (dimensions, distance metric) after an index is created. You must create the Qdrant collection manually before running the migration.</aside>
|
|
|
|
## Concept Mapping
|
|
|
|
| Redis | Qdrant | Notes |
|
|
| :--- | :--- | :--- |
|
|
| FT Index | Collection | One-to-one mapping |
|
|
| Document | Point | Each document becomes a point |
|
|
| Vector field | Vector | Named vectors are preserved |
|
|
| Hash/JSON fields | Payload | Direct mapping |
|
|
| Document key | Payload field | Stored via `--qdrant.id-field` |
|
|
|
|
## Run the Migration
|
|
|
|
```bash
|
|
docker run --net=host --rm -it registry.cloud.qdrant.io/library/qdrant-migration redis \
|
|
--redis.index 'your-ft-index' \
|
|
--redis.addr 'localhost:6379' \
|
|
--qdrant.url 'https://your-instance.cloud.qdrant.io:6334' \
|
|
--qdrant.api-key 'your-qdrant-api-key' \
|
|
--qdrant.collection 'your-collection'
|
|
```
|
|
|
|
### With Authentication
|
|
|
|
```bash
|
|
docker run --net=host --rm -it registry.cloud.qdrant.io/library/qdrant-migration redis \
|
|
--redis.index 'your-ft-index' \
|
|
--redis.addr 'your-redis-host:6379' \
|
|
--redis.username 'your-username' \
|
|
--redis.password 'your-password' \
|
|
--qdrant.url 'https://your-instance.cloud.qdrant.io:6334' \
|
|
--qdrant.api-key 'your-qdrant-api-key' \
|
|
--qdrant.collection 'your-collection' \
|
|
--migration.create-collection false
|
|
```
|
|
|
|
### All Redis-Specific Flags
|
|
|
|
| Flag | Required | Description |
|
|
| :--- | :--- | :--- |
|
|
| `--redis.index` | Yes | RediSearch FT index name |
|
|
| `--redis.addr` | No | Redis address (default: `localhost:6379`) |
|
|
| `--redis.protocol` | No | Redis protocol version (default: `2`) |
|
|
| `--redis.username` | No | Username for authentication |
|
|
| `--redis.password` | No | Password for authentication |
|
|
| `--redis.client-name` | No | Client name |
|
|
| `--redis.db` | No | Database number |
|
|
| `--redis.network` | No | Network type: `tcp` or `unix` (default: `tcp`) |
|
|
|
|
### Qdrant-Side Options
|
|
|
|
| Flag | Default | Description |
|
|
| :--- | :--- | :--- |
|
|
| `--qdrant.id-field` | `__id__` | Payload field name for original Redis document keys |
|
|
|
|
## Gotchas
|
|
|
|
- **Named vectors:** If your Redis index has multiple vector fields, all are migrated as named vectors. Ensure your pre-created Qdrant collection has a matching named vector configuration.
|
|
- **ID mapping:** Redis document keys are converted to Qdrant point IDs. The original key is stored in the payload under `--qdrant.id-field`.
|
|
|
|
## Next Steps
|
|
|
|
After migration, verify your data arrived correctly with the [Migration Verification Guide](/documentation/migration-guidance/).
|