Uploaded image for project: 'SlamData'
  1. SlamData
  2. SD-919

mongodb: always error when collection doesn’t exist

    Details

    • Type: Bug
    • Status: Done
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: 2.1
    • Fix Version/s: 2.3
    • Component/s: Quasar
    • Labels:

      Description

      When we use mapReduce, MongoDB raises an exception saying there’s no collection, but for the aggregation pipeline, it just returns zero results.

      These should both error, using the same SD Error.

      I don’t know whether it makes more sense to always pre-check existence when we have a pipeline, or if we should only check after we get an empty result set back.

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                jr Jean-Remi Desjardins
                Reporter:
                greg Greg Pfeil
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: