spring-projects / spring-projects/spring-data-jpa

Upgrade to Jakarta Persistence 4.0

Open

#4,187 opened on Feb 11, 2026 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

theme: JPA-4.0 type: enhancement

Dominant language: Java
Stars: 3.3k
Forks: 1.6k
PR merge metrics: No merged PRs in 30d

Description

Upgrade to the Jakarta Persistence API 4.0

Replace executeUpdate calls on Query, to be replaced with Statement.execute
Revisit for-removal deprecations on Query (getResult*() methods, setCache*(…) methods, setLockMode(), setMaxResult, setFirstResult methods)
Investigate where we could use TypedQuery and introduce wrappers to defer calls to the Query interface

Contributor guide

Open the contributing 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 usages of Query.executeUpdate, the listed deprecated Query methods, and existing TypedQuery handling in the repository. Review how these calls are used before determining the required Jakarta Persistence 4.0 changes; done means the API upgrade is complete, deprecated usages are addressed, and suitable Query wrappers are introduced where needed.

Written by the indexing model from the issue text.

Assessment

Tech stack: java, spring
Domain: backend, database
Issue type: Refactor
Difficulty: 4/5
Estimated time: 3-5 days
Activity status: Quiet
Clarity: Needs clarification
Newbie friendliness: 42/100

A short digest of beginner-friendly GitHub issues.