MapReduce does not respect existing shard key on output:sharded

XMLWordPrintableJSON

    • Query
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Backlog - Query Team (Inactive)
            Reporter:
            Scott Hernandez (Inactive)
            Votes:
            6 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: