spring-projects / spring-projects/spring-ai

Support Redis 8 native vectorset (VADD/VSIM) as a VectorStore implementation

Open
#6,819 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: waiting-for-triage
Dominant language
Java
Stars
9.5k
Forks
2.9k
Avg merge
1d 7h
Merged PRs (30d)
6

Description

Feature Request

Redis 8 ships with a native vector type (vectorset) using the VADD and VSIM
commands, available out of the box without Redis Stack or the RediSearch module.

The current RedisVectorStore implementation requires RediSearch (FT.CREATE /
FT.SEARCH), which means users on standard Redis 8 (e.g. installed via brew, or
hosted Redis 8 on cloud providers) cannot use it.

Request: Add a RedisVectorSetVectorStore (or extend the existing one) that
uses the new VADD/VSIM API.

Motivation:

  • Redis 8 is the current stable release
  • vectorset is built-in — no extra module, no Redis Stack needed
  • Spring AI users on Redis 8 have no path to use Redis as a vector store today

References:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the existing RedisVectorStore implementation and its FT.CREATE/FT.SEARCH usage, then consult the linked Redis vectorset documentation for VADD and VSIM behavior. Done means a Redis 8 vectorset-backed VectorStore path is available without Redis Stack or RediSearch, with the relevant tests added or updated.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, redis, spring
Domain
backend, databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.