-
Type:
Improvement
-
Resolution: Done
-
Priority:
Minor - P4
-
None
-
Affects Version/s: 2.0.2
-
Component/s: Index Maintenance
-
None
-
Environment:WIN C#
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
Not sure if this is by design, a bug, or whether I am doing something wrong, but see findings in this thread:
https://groups.google.com/forum/#!topic/mongodb-user/_3e0fmVorD0
The use case where this comes into play is explained in the thread: "Using unset on a sparse index as an archiving alternative to two collections".