spring-projects / spring-projects/spring-data-mongodb
Improve Query/Update property mapping.
Open
Nobody has claimed this yet.
status: pending-design-work
- Dominant language
- Java
- Stars
- 1.7k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
The current KeyMapper implementation should be improved by making use of Persistent | PropertyPath to avoid keeping track of individual key fragments while mapping the target key.
relates to: #3688
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 by locating the KeyMapper implementation and reading the related issue #3688. Trace how query and update property mappings currently track key fragments, then verify that the mapping uses Persistent | PropertyPath and preserves the expected target-key behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, mongodb
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100