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

utilize index for full collection scan in some cases

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Querying
    • Labels:
      None
    • Query
    • ALL

      described in an email to me as:

      { x : <anything> }

      including not, $or, regex, whatever, sometimes just scanning the whole index would be better than a table scan. i assume query optimizer is not testing that plan at the moment (with minkey and maxkey the full range)? should we do that?

            Assignee:
            backlog-server-query Backlog - Query Team (Inactive)
            Reporter:
            aaron Aaron Staple
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: