-
Type:
Bug
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Duplicate
-
Affects Version/s: 2.6.1
-
Fix Version/s: None
-
Component/s: Storage
-
Labels:None
-
Operating System:ALL
-
Steps To Reproduce:
capped collections in earlier versions of mongodb (2.4.x) can sometimes look like this:
{ "name" : "test-1.two", "options" :
},
when a database with a capped collection like that is upgraded to 2.6.1, and then a copydatabase is run against it, the copy database succeeds, but the capped collections are not copied properly
- duplicates
-
SERVER-13976 Cloner needs to detect failure to create collection
-
- Closed
-
- is related to
-
SERVER-13737 CollectionOptions parser should skip "size"/"max" elements if values non-numeric
-
- Closed
-
- related to
-
SERVER-13968 Report invalid collection options in "<db>.system.namespaces" in upgrade checker
-
- Closed
-