[SERVER-53664] Architecture Guide: add a "Catalog Change Isolation" section to the greater "Catalog" section Created: 08/Jan/21 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Sprint: | Execution Team 2022-02-07, Execution Team 2022-02-21 |
| Participants: |
| Description |
|
Or perhaps modify the "Catalog Changes, versioning and the Minimum Visible Snapshot" section. Discuss DDL operation isolation in the copy-on-write world – createCollection already basically did this, to get create into multi-doc transactions, now drop and rename do as well. |