Re-enable map_reduce_invalid_output_collection.js for non-aggregation mapReduce

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Query
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      map_reduce_invalid_output_collection.js verifies a mapReduce merging to an already sharded collection will fail if that collection is not sharded by _id. For non-aggregation mapReduce, this relies on upserts without the full shard key being rejected (see SERVER-42916). SERVER-44382 allowed upserted documents in a sharded collection to have missing shard key fields, so the non-aggregation mapReduce cases in the test were disabled. They should be re-enabled after determining how mapReduce to a collection sharded by a key other than _id should behave.

            Assignee:
            Backlog - Query Team (Inactive)
            Reporter:
            Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: