[SERVER-63788] Clarify write semantics of various CollectionCatalog methods Created: 17/Feb/22 Updated: 26/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | catalog, oldstorexemea, techdebt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Currently we have a relatively confusing state where some static methods on the CollectionCatalog have write semantics. They do not modify the current instance, but they call CollectionCatalog::write, either immediately or asynchronously on commit via UncommittedCatalogUpdates. We might be able to refactor this in some way to make it clearer what the write semantics are. |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 23/Feb/22 ] |
|
Linking SERVER-63679 to keep in mind. |