If you shard a collection with a key like {{
{"a.b":1}}} the system stores that as a field name in various collections (collections, chunks, changelog and tags to name a few).
This causes problems with backing up and restoring data or moving data to other databases (since these fields are invalid as user documents). It also means that the clients/driver and server has to special case these collections (or database) to disable regular validation (hence the problem moving this data to user collections).
This is somewhat related to trying to copy the profiler documents (which have fields with $prefix or dots) to different collections.
- related to
-
SERVER-24174 Inconsistent rule for storing dotted field names
- Closed
-
SERVER-29334 Cannot write shard chunks documents with _id fields containing values with dotted field names, e.g. { _id: { a.b: 10 } }
- Closed
-
SERVER-3943 $quote operator
- Closed