[SERVER-59851] Investigate whether BSON depth validation logic can be consolidated Created: 09/Sep/21 Updated: 20/Oct/21 Resolved: 20/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Gregory Noma |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | techdebt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Sprint: | Execution Team 2021-11-01 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Currently we have two separate implementations to validate the depth of a BSON object: one used by inserts and one used by updates. This can lead to discrepancies like the one described in However, this may not be possible due to performance reasons. In particular, the update path uses mutablebson to do the traversal whereas the insert path does not.. |
| Comments |
| Comment by Gregory Noma [ 20/Oct/21 ] |
|
Going to close this in favor of SERVER-60158, which should cover this plus more general cases as well. |