[SERVER-62573] Update the CollectionCatalog class' documentation around what is safe usage with/without a collection lock Created: 12/Jan/22 Updated: 02/Mar/23 Resolved: 02/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Sprint: | Execution Team 2022-02-21, Execution Team 2022-05-30 | ||||||||
| Participants: | |||||||||
| Description |
|
I often receive inquires regarding how to use various CollectionCatalog functions. The comments are mostly out of date since we made Collection copy-on-write and then CollectionCatalog copy-on-write. It's difficult, both team internally and team externally, to know what usage is safe to do and what the repercussions may be. |