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

Issues with multiple spatial indexes

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 1.9.2
    • Component/s: Geo
    • Labels:
      None
    • ALL

      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.

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

              Created:
              Updated:
              Resolved: