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

interleaved cursor results may contain some matches from non sparse index and some from sparse index

    XMLWordPrintableJSON

Details

    • Icon: Question Question
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None

    Description

      Currently we have different matching semantics for sparse vs non sparse indexes (since sparse indexes don't contain documents lacking the indexed field, those are not returned). With cursor interleaving in the query optimizer, if two indexes are used and one is sparse while the other is not, some documents may be loaded from each index. The resulting matching semantics will not be the same as the current sparse or non sparse matching semantics.

      Attachments

        Activity

          People

            Unassigned Unassigned
            aaron Aaron Staple
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: