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

Issues with multiple spatial indexes

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Duplicate
    • Affects Version/s: 1.9.2
    • Fix Version/s: None
    • Component/s: Geo
    • Labels:
      None
    • Operating System:
      ALL

      Description

      We currently say in the docs that we allow only one spatial index per collection. However:

      • It's possible to create more than on spatial index on a collection, and $near queries seem to work on them.
      • geoNear commands always fail when there's more than one spatial index.

      We should either:

      • Enforce the single spatial index constraint

      or

      • Allow the user to specify which field to search using the geoNear command, and remove the limitation from the docs.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              hari.khalsa@10gen.com hari.khalsa@10gen.com
              Reporter:
              kbanker Kyle Banker
              Participants:
              Votes:
              5 Vote for this issue
              Watchers:
              10 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: