[SERVER-6884] Refactor capped collection code Created: 29/Aug/12 Updated: 06/Dec/22 Resolved: 16/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Ben Becker | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | refactor | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
There's currently a lot of ambiguous overlap in the capped and non-capped collection code. Reading through the allocate/delete/overrun logic can be quite time consuming. There are also various portions of the storage system which have multiple branches of logic specifically to deal with capped collections, which may not need to be there. It might be worth considering any future use-cases, like |