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

Avoid reading the special dense column if reading a known to be dense path

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • QE 2022-11-14, QE 2022-11-28, QE 2022-12-12, QE 2022-12-26

      Currently, the column_scan stage always reads the special dense column in absence of filters. There are two issues to consider:

      1. In some cases (e.g. if "_id" column is also being read) reading the dense column isn't needed for correctness and we should avoid it.
      2. Should the decision to use the dense column belong to the scan_stage or to its clients?

            Assignee:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Reporter:
            irina.yatsenko@mongodb.com Irina Yatsenko (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: