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

MapReduce does not allow limit as one attribute on a sharded setup

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: 1.6.3
    • Fix Version/s: None
    • Component/s: MapReduce
    • Labels:
      None
    • Environment:
      OS - Linux hqd-soak-03 2.6.18-164.11.1.el5 #1 SMP Wed Jan 20 07:32:21 EST 2010 x86_64 x86_64 x86_64 GNU/Linux
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      Linux

      Description

      We have sharded setup on 2 machines and have a 120GB collection on these machines.

      Ran a mapreduce job through db.runCommand with a limit attribute, to test the map-reduce functions and it did threw an error message that limit attribute is not allowed.

      Specifics

      db.runCommand({mapreduce: "bigdm",
      map:m,
      reduce: r,
      limit:100,
      query: { "dynamicRL" : { "$exists" : true}},
      out: "dt",
      verbose: true});

      It gives me following error message

      {
      "assertion" : "don't know mr field: limit",
      "assertionCode" : 10177,
      "errmsg" : "db assertion failure",
      "ok" : 0
      }

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                2 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: