-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
ALL
-
v4.4
-
Sharding 2020-03-23
-
50
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Additionally, write a test that confirms that we don't allow renaming unsharded collections across databases with different primary shards (i.e. catches this error here, though that check is on mongos against mongos's routing table cache, and therefore racy).