-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Query
-
ALL
-
(copied to CRM)
If you output into an existing sharded collection then the shard key is not changed but data is still written to a shard – if the shard key is anything but {_id: 1} this is a problem. This results in all of the data being "unowned" and filtered out from queries, and it looking like the sharded collection is empty.
There are probably many more nuances here, and places where things are broken, so more time should be taken to investigate all behaviors if there is an existing sharded collection, or simply disallow that option until we can define and fix all behaviors.
- duplicates
-
SERVER-16605 Mapreduce into sharded collection with hashed index fails
- Closed
- is duplicated by
-
SERVER-22060 Sharded mapReduce output option {replace: "coll", sharded: true} can create an invalid sharded collection
- Closed
-
SERVER-28321 In mapReduce map function emitting a document with 'undefined' or 'null' key in sharded collection fails
- Closed
- is related to
-
SERVER-12581 mapReduce sharded output replace does not fully split
- Closed
- related to
-
SERVER-12261 Map Reduce with sharded output collection creates orphan documents
- Closed