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

Special index types including hashed indexes not always used when they should be

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.3.2
    • Component/s: Querying
    • Labels:
      None
    • Operating System:
      ALL

      Description

      If a special index type is hinted but is not considered "suitable", the code in QueryPlan::newCursor instantiates its own btree rather than just handing off to the custom "newCursor" code for that index. This is probably incorrect behavior (I believe the btree bounds that it comes up with can be incorrect for special indexes). One way to to fix this is to initialize "_type" earlier, and make sure the custom newCursor methods handle being used for unsuitable queries.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: