Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-45211

Sharded cluster fails on mapReduce with output collection when namespace does not yet exist

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: MapReduce
    • Labels:
      None
    • Query

      A Java driver test of mapReduce to a non-existent database exposes a difference in behavior between latest builds and the 4.2 release. We're seeing this error:

      {
   "ok": 0.0, 
   "errmsg": "database output-2284299633124 not found", 
   "code": 26, 
   "codeName": "NamespaceNotFound"

      on latest sharded clusters. The test succeeds on all released versions of MongoDB.

            Assignee:
            backlog-server-query Backlog - Query Team (Inactive)
            Reporter:
            jeff.yemin@mongodb.com Jeffrey Yemin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: