[SERVER-60158] Generalize BSONObj traversal code from bson validate Created: 22/Sep/21 Updated: 06/Nov/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Henrik Edin | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | former-storex-namer | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
The BSON traversal code used by bson validate is written with performance in mind to allow for high throughput. If we separate the code for traversing the binary and validating it (while still maintaining inlining/performance for validate) it should allow us to write custom validate functions that can be used to scan BSON binaries in an efficient way. It could be used to implement storage_validation::storageValid for example. |