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

Capture actual error from getExecutor

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.5.10
    • Affects Version/s: None
    • Component/s: Querying
    • Fully Compatible
    • Query 2017-07-10

      After getExecutor() was enhanced to return an actual Status instead of a bool, not all callers were changed to capture and return this new status. For example, today, the geoNear command can still return this:

      { waitedMS: 0, ok: 0.0, errmsg: ”can’t get query executor” }
      

      I believe the mapReduce command has similar issues.

            Assignee:
            natalia.jacobowitz Natalia Jacobowitz
            Reporter:
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: