spring-projects / spring-projects/spring-data-jpa
Add support for `@Static[Native]Query(…)`, `@ReadQueryOptions` and `@WriteQueryOptions`
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3.3k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
JPA 4.0 introduces new annotations to declare queries and query options on the method level, mostly to cater for Jakarta Data repositories. It would make sense to support these as alternatives to @Query/@NativeQuery and @QueryHint.
RepositoryInformationSupport.isQueryAnnotationPresentOn() requires special consideration as @StaticQuery is not a Spring-managed annotation.
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 at RepositoryInformationSupport.isQueryAnnotationPresentOn(), then trace how existing @Query, @NativeQuery and @QueryHint annotations are detected and applied. Add support for the four JPA 4.0 annotations, including the special handling needed for @StaticQuery, and verify the repository annotation behavior with the project’s relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100