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

Optimise queries to cover on sharded clusters when using compound hashed index

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.3.3
    • None
    • None
    • None
    • Fully Compatible
    • Query 2020-01-13, Query 2020-01-27

    Description

      When compound hashed shard key has a range prefix, if the query predicate is on the prefix and the projection doesn't include hashed fields then the query can be covered.

      The current behaviour for hashed shard keys is, we always fetch the documents on the shards to make sure that the document is not an orphan. When the projection and query doesn't include hashed fields, the document fetch can be avoided.

      Attachments

        Activity

          People

            arun.banala@mongodb.com Arun Banala
            arun.banala@mongodb.com Arun Banala
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: