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

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 2.3.2
    • Querying
    • None
    • 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

              Unassigned Unassigned
              matulef Kevin Matulef
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: