spring-projects / spring-projects/spring-data-rest
PUT vs PATCH with JPA
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 958
- Forks
- 568
- PR merge metrics
- No merged PRs in 30d
Description
When using PUT method, removing any field appears to be interpreted as "no change".
This seems to be close to the expected behavior of PATCH method, not PUT.
Example:
Step 1 GET /objects/o1 { "f1":"v1", "f2":"v2"}
Step 2 PUT /objects/o1 { "f1":"v1"}
Step 3 GET /objects/o1 { "f1":"v1", "f2":"v2"}
(it seems that the result should be { "f1":"v1"})
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
Reproduce the three-step PUT sequence from the issue and compare it with PATCH behavior in Spring Data REST's request handling. Trace how omitted fields are treated with JPA, then verify that PUT removes the omitted field while PATCH retains it, as reflected by the final GET response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100