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

Investigate whether InternalPlans::indexScan() executor always scans forward

XMLWordPrintableJSON

    • Type: Icon: Question Question
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.3.0
    • Affects Version/s: None
    • Component/s: Query Execution, Sharding
    • None
    • Fully Compatible
    • QE 2021-08-23, QE 2021-09-06, Sharding EMEA 2021-11-29, Sharding EMEA 2021-12-13, Sharding EMEA 2021-12-27

      Investigate whether subsequent calls of getNextDocument can result in scanning a key lower than the previous one.

      The guess would be that this is not possible because index keys are sorted and - in case of yielding - it can at most happen for some previous key to be lost.

      Opening this ticket to double check because SERVER-20700 introduced an additional sorting of the splitVector result (vector of keys filled in with subsequent getNextDocument calls), so it would be worth checking if the original bug is still around.

            Assignee:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: