Support Redis native Vector Sets (VADD/VSIM) as migration source
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 82
- Forks
- 21
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 16
Description
The Redis migration tool currently requires --redis.index pointing to a RediSearch FT index. This makes it incompatible with deployments that use Redis's native Vector Set type instead of the RediSearch module. Clusters using Vector Set type (VADD / VSIM / VREM) with no RediSearch module installed have no migration path with the current tool.
The tool should support Redis native Vector Sets as an alternative source, enumerating vectors via the native Vector Set commands:
VCARD — count members
VRANDMEMBER — iterate members
VEMB — retrieve vector embeddings
VGETATTR — retrieve associated attributes/metadata
Add an optional mode (e.g. --redis.source=vectorset) that enumerates and reads from native Vector Sets rather than requiring an FT index.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the Redis migration source handling and CLI option parsing, then trace how the existing FT index source enumerates records. Done means an optional vectorset mode uses VCARD, VRANDMEMBER, VEMB, and VGETATTR to migrate native Vector Set data without RediSearch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, redis
- Domain
- cli, data, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100