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

SBE stagebuilders should treat metadata uniformly

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution

      This is an idea for a simplification in SBE stagebuilders. Currently we have struct PlanStageMetadataSlots with a handful of fields for some of the document metadata fields. In PlanExecutorSBE::initializeAccessors we handle most of them the same way, except for sortKeySlot which has a special case I'm not familiar with.

      Could we replace this with a single `map< MetaType, SlotId >`, and handle all meta fields the same way? This would make SBE unaware of the specific meanings of the different meta fields, which seems like a good thing for modularity: SBE provides low level execution, and higher layers can put whatever data they want into it.

      I noticed this while reviewing SERVER-99589.

            Assignee:
            Unassigned Unassigned
            Reporter:
            david.percy@mongodb.com David Percy
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: