[SERVER-69360] Remove small field optimization of damages computation Created: 01/Sep/22 Updated: 29/Oct/23 Resolved: 09/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jordi Olivares Provencio | Assignee: | Jordi Olivares Provencio |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2022-09-19 |
| Participants: |
| Description |
|
There is a small field optimization whenever we compute damages that will treat the field + value as part of a damage. This is meant to reduce the total number of damages as it would help merge nearby damages if they are only separated by a small field. However, this can cause potential runoffs if all the fields are considered small, leading to all of them being considered as part of a damage. In some instances this can cause a single damage to contain 90%+ of the original document even if it only modified a few bytes initially. To avoid this the optimization should be removed. |
| Comments |
| Comment by Githook User [ 09/Sep/22 ] |
|
Author: {'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}Message: |