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

More specific explain() for geo queries

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 1.8.1
    • 2.1.0
    • Geo
    • None
    • ALL

    Description

      Suppose you have two compound geo indexes defined on the same collection. For instance:

      {loc: '2d', day: 1} {loc: '2d', year: 1}

      Currently, the explain() output for queries that should use these indexes is deficient the following ways:

      1. The exact index being used isn't noted. All we get is the cursor type: GeoSearchCursor.

      2. The index bound aren't provided for either field. This makes it impossible to know whether the compound index is even worth maintaining.

      For instance:

      "cursor" : "GeoSearchCursor",
      "nscanned" : 1,
      "nscannedObjects" : 1,
      "n" : 1,
      "millis" : 0,
      "nYields" : 0,
      "nChunkSkips" : 0,
      "isMultiKey" : false,
      "indexOnly" : false,
      "indexBounds" : {}

      Attachments

        Issue Links

          Activity

            People

              greg_10gen Greg Studer
              kbanker Kyle Banker
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: