[SERVER-37215] Do not allow a collection to be created with the UUID of an existing collection Created: 19/Sep/18 Updated: 27/Oct/23 Resolved: 07/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Daniel Gottlieb (Inactive) |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | execution_intern_2019, nyc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Sprint: | Execution Team 2019-08-12 | ||||
| Participants: | |||||
| Linked BF Score: | 51 | ||||
| Description |
|
There are no assertions, invariants, or errors thrown in DatabaseImpl::createCollection if a collection is created using the UUID of a collection that already exists in the UUIDCatalog. Creating a new collection with an existing UUID results in theĀ UUIDCatalog::onCreateCollection observer removing the entry of the previous collection. This allows two collections to exist with the same UUID. In the case of two-phase collection drops, this can result in no collections registered to a UUID, despite existing. |
| Comments |
| Comment by Daniel Gottlieb (Inactive) [ 07/Aug/19 ] |
|
There have been changes since this ticket was created that have added the requested invariant. |