spring-projects / spring-projects/spring-ai
PgVectorStore queries customization.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.5k
- Forks
- 2.9k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 5
Description
I want to extend PgVectorStore queries. (e.g. to limit searches only to vectors to which user has access to.)
Current Behavior
Current approach copies existing code of PgVectorStore to a new class.
Expected Behavior
Queries should be constructed by external configurable bean.
Context
I want to implement limitations on the top of PgVector similarity search queries to limit access to data.
How has this issue affected you?
I had to copy a lot of code.
What are you trying to accomplish?
Simplifying query construction.
What other alternatives have you considered?
I would expect alternatives as outcome of the discussion.
Are you aware of any workarounds?
yes.
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
Start by locating PgVectorStore and its similarity-search query construction, then compare it with the referenced IdentityAwarePgVectorStore example. Determine the configurable extension point needed for access limitations; done means callers can customize query construction without copying the existing store implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, postgresql, spring
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100