spring-projects / spring-projects/spring-ai
Auto-configuration dependency issues and ignoring vector databases can cause auto-configuration to not take effect
Open
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
org.springframework.ai
spring-ai-starter-vector-store-elasticsearch
co.elastic.clients
elasticsearch-java
co.elastic.clients
elasticsearch-java
9.0.2
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
The issue provides a Maven dependency override for spring-ai-starter-vector-store-elasticsearch and elasticsearch-java 9.0.2, but names no source files or tests. Start by locating the Elasticsearch vector-store auto-configuration and dependency metadata, then reproduce the override; done means auto-configuration still takes effect and the vector database is not ignored.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, java, spring
- Domain
- backend, build-system, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100