spring-projects / spring-projects/spring-data-mongodb
BUG: update document was broken when key is like `child.mapmap.1012.2`
Open
Nobody has claimed this yet.
status: waiting-for-triage
- Dominant language
- Java
- Stars
- 1.7k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
when I try to make an update { $set: { "a.b.1.2": 1 } }, the actually executed update was { $set: { "a.b.1": 1 } }.
minimal reproduce
https://github.com/hu-chia/minimal-reproduce-to-mongo-update-be-broken.git
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 with the linked minimal reproduction, especially src/test/java/com/example/mongoupdate/TestMongoUpdateApplication.java at line 30, and inspect how the update key is represented and executed. Verify that the full nested key a.b.1.2 is preserved rather than reduced to a.b.1; done means the reproduction performs the intended MongoDB update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, mongodb, spring
- Domain
- backend, database
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100