Use MongoDB projection API instead of FieldSelector class [DBZ-2702]
- Dominant language
- HTML
- Stars
- 6
- Forks
- 8
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-2702](https://issues.redhat.com/browse/DBZ-2702)
I'm working on This issue and during this issue DBZ-2447, I found the FieldSelector class.
In my opinion, we should remove this class and use the MongoDB projection API.
because it's simple, easy to use, supports complex projection, and also it doesn't need to catch the whole document at first and then parse the document and remove/rename the fields of the document.
Contributor guide
Research direction
Start by locating the FieldSelector class and reviewing the related DBZ-2447 context. Compare its current behavior with MongoDB's projection API, including complex projections and field removal or renaming. Done means FieldSelector is removed and projection handling uses the MongoDB API without fetching the whole document first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mongodb
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100