-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Catalog
-
None
-
Storage Execution
-
ALL
-
-
0
Noticed a build failure whose root cause is that we allow user collections to get renamed to a valid system collections if the target system collection is not present. As a result, that system collection can have docs that would violate the index key constraints when it's indexes gets built in future, leading to fassert failure. But, on the other hand, if the target system collection is present, then we would fail the rename either due to
1) 'NamespaceExists' error if 'droptarget' param of rename cmd is set as false.
2)'can't drop system collection <system collection name>' error if droptarget param of rename cmd is set true.
- duplicates
-
SERVER-5955 Forbid renaming system collections
- Closed
- is duplicated by
-
SERVER-5955 Forbid renaming system collections
- Closed